Sub-URI setup with 4.1

Added by Thomas Jahns 5 months ago

Hello,

I've been running redmine 3.4.12 with a sub-uri setup (where redmine appears at /redmine).

So far I've failed to replicate this with 4.1.1 after upgrading:

#32318 and #31085 were of no help, I always get a route error like this

Started GET "/redmine/" for REDACTED at 2020-05-26 03:33:57 +0200

ActionController::RoutingError (No route matches [GET] "/redmine"):

vendor/bundle/ruby/2.3.0/gems/actionpack-5.2.4.2/lib/action_dispatch/middleware/debug_exceptions.rb:65:in `call'
vendor/bundle/ruby/2.3.0/gems/actionpack-5.2.4.2/lib/action_dispatch/middleware/show_exceptions.rb:33:in `call'
vendor/bundle/ruby/2.3.0/gems/railties-5.2.4.2/lib/rails/rack/logger.rb:38:in `call_app'
vendor/bundle/ruby/2.3.0/gems/railties-5.2.4.2/lib/rails/rack/logger.rb:26:in `block in call'
vendor/bundle/ruby/2.3.0/gems/activesupport-5.2.4.2/lib/active_support/tagged_logging.rb:71:in `block in tagged'
vendor/bundle/ruby/2.3.0/gems/activesupport-5.2.4.2/lib/active_support/tagged_logging.rb:28:in `tagged'
vendor/bundle/ruby/2.3.0/gems/activesupport-5.2.4.2/lib/active_support/tagged_logging.rb:71:in `tagged'
vendor/bundle/ruby/2.3.0/gems/railties-5.2.4.2/lib/rails/rack/logger.rb:26:in `call'
vendor/bundle/ruby/2.3.0/gems/actionpack-5.2.4.2/lib/action_dispatch/middleware/remote_ip.rb:81:in `call'
vendor/bundle/ruby/2.3.0/gems/request_store-1.4.1/lib/request_store/middleware.rb:19:in `call'
vendor/bundle/ruby/2.3.0/gems/actionpack-5.2.4.2/lib/action_dispatch/middleware/request_id.rb:27:in `call'
vendor/bundle/ruby/2.3.0/gems/rack-2.2.2/lib/rack/method_override.rb:24:in `call'
vendor/bundle/ruby/2.3.0/gems/rack-2.2.2/lib/rack/runtime.rb:22:in `call'
vendor/bundle/ruby/2.3.0/gems/activesupport-5.2.4.2/lib/active_support/cache/strategy/local_cache_middleware.rb:29:in `call'
vendor/bundle/ruby/2.3.0/gems/actionpack-5.2.4.2/lib/action_dispatch/middleware/executor.rb:14:in `call'
vendor/bundle/ruby/2.3.0/gems/actionpack-5.2.4.2/lib/action_dispatch/middleware/static.rb:127:in `call'
vendor/bundle/ruby/2.3.0/gems/rack-2.2.2/lib/rack/sendfile.rb:110:in `call'
vendor/bundle/ruby/2.3.0/gems/rack-2.2.2/lib/rack/content_length.rb:17:in `call'
vendor/bundle/ruby/2.3.0/gems/railties-5.2.4.2/lib/rails/engine.rb:524:in `call'
vendor/bundle/ruby/2.3.0/gems/railties-5.2.4.2/lib/rails/railtie.rb:190:in `public_send'
vendor/bundle/ruby/2.3.0/gems/railties-5.2.4.2/lib/rails/railtie.rb:190:in `method_missing'
/some/system/path/redmine/public/dispatch.fcgi:16:in `call'
vendor/bundle/ruby/2.3.0/gems/rack-2.2.2/lib/rack/handler/fastcgi.rb:68:in `serve'
vendor/bundle/ruby/2.3.0/gems/rack-2.2.2/lib/rack/handler/fastcgi.rb:28:in `block in run'
vendor/bundle/ruby/2.3.0/gems/rack-2.2.2/lib/rack/handler/fastcgi.rb:27:in `each'
vendor/bundle/ruby/2.3.0/gems/rack-2.2.2/lib/rack/handler/fastcgi.rb:27:in `run'
/some/system/path/redmine/public/dispatch.fcgi:20:in `<main>'

The system uses Debian buster with the older ruby 2.3 from stretch (because 2.5 isn't listed as supported in redmine 3.4), bundle commands have run fine, just the sub-uri part seems to have problems.

$ bundle exec rails --version
Rails 5.2.4.2

The DB is postgres 11, the web-server is lighttpd with fcgi.

Replies (1)

RE: Sub-URI setup with 4.1 - Added by Thomas Jahns 5 months ago

So I've not given the probably most important detail: I'm using an fcgi setup with lighttpd. So I don't automatically get the stuff from config.ru and the recipe from https://stackoverflow.com/questions/4906205 does not immediately help because the invocation at the end of public/dispatch.fcgi differs significantly.

(1-1/1)