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

Support customizing session cookie name. #7072

Closed
wants to merge 1 commit into from

Conversation

hsldymq
Copy link

@hsldymq hsldymq commented Jun 12, 2024

What scenarios require custom session cookie names?

When multiple AdGuard Home instances are running on a host, having the same IP or domain name, only the port is different, you cannot log in to the web UI of two instances at the same time, because they use the same session cookie name. . After logging into instance A, logging in to instance B will cause the login status on instance A to be invalid.

#4680 and #1196 also mentioned this problem.

@hsldymq
Copy link
Author

hsldymq commented Dec 11, 2024

Hi @ainar-g , could you please have a look at this PR

@ainar-g
Copy link
Contributor

ainar-g commented Dec 11, 2024

Good day. As recommended in the contribution guidelines, it's better to discuss a change before contributing any code. Currently, we think that it's the job of the reverse proxy (i.e. Nginx) to handle header mutations for unusual configurations, so we'd rather not add complexity for that.

@ainar-g ainar-g closed this Dec 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants