Redirecting after an authentication error

Open
#218 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
28/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
mysql, nginx
Domain
authentication, backend

Research direction

Start by reproducing the authentication-error and successful-signup redirects in the NGINX-proxied HTTPS setup, checking the configured base URL and redirect handling. Trace the login/auth and signup paths to identify why redirects use port 80; done means both flows preserve HTTPS and port 443.

Written by the indexing model from the issue text.

Description

Bug

My NGINX is set to redirect all HTTP traffic to HTTPS, on port 443. When someone enters their credentials wrongly, they get redirected to port 80 (blabla.com:80/login/auth?login_error=1) instead of 443, which is specified in the base URL. This is also happening when people successfully sign up, they get redirected to blabla.com:80.

Is there a way to fix this, as not a lot of people are running an HTTPS only environment. Thanks.

PS: this is running 1.0.6 with MySQL behind an NGINX proxy.

Dominant language
JavaScript
Stars
9.8k
Forks
978
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from streamaserver/streama

All issues in streamaserver/streama

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.