Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow other http_origin (to use behind reverse proxy) #43

Open
caimandepamer opened this issue Nov 25, 2024 · 0 comments
Open

Allow other http_origin (to use behind reverse proxy) #43

caimandepamer opened this issue Nov 25, 2024 · 0 comments
Assignees
Labels
bug Something isn't working

Comments

@caimandepamer
Copy link

caimandepamer commented Nov 25, 2024

Problem:
When using the APP behind a reverse proxy, the "http_origin" is different than the original, ex:
Directly: http://tududi:9292
RProxied: https://tududi
So the "Rack::Protection" statement prevents the login.

Example:
log from the docker: WARN -- : session dropped by Rack::Protection::HttpOrigin

Work Arround:

step 1: Script created "patchApp.sh" with content:

#!/bin/bash
sed -i s/Protection/'Protection, except: [:http_origin]'/g /usr/src/app/app.rb

step 2: Add the "command" statement in the compose file:

      `command: /bin/sh -c "/custom-cont-init.d/patchApp.sh  && rake db:migrate && puma -C app/config/puma.rb" `

Other problems:
This allows to login but still prevents to create tasks, projects, etc... with the log:
WARN -- : session dropped by Rack::Protection::HttpOrigin
and I can not find there is the other "Protection" statement.

Thank you for this beautiful app!!!!

@chrisvel chrisvel self-assigned this Nov 25, 2024
@chrisvel chrisvel added the bug Something isn't working label Nov 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants