sameersbn / sameersbn/docker-gitlab
stop redirecting port 80 to port 443 when certificate is used.
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 8.1k
- Forks
- 2.1k
- Avg merge
- 17h 47m
- Merged PRs (30d)
- 7
Description
According to document, "In this configuration, any requests made over the plain http protocol will automatically be redirected to use the https protocol. However, this is not optimal when using a load balancer." , I was wondering if we could choose stop redirecting 80 to 443? We could like to keep port 80 for insecure content and port 443 for secure content.
Right now, it seems to me that all requests which send to port 80 will be redirect to port 443 automatically. Is it possible to stop redirecting? Any ideas are welcome.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No file, test, or entry point is named. Start by locating the certificate and HTTP/HTTPS port configuration described in the documentation, then determine where the port 80 redirect is configured; done means port 80 can serve insecure content without redirecting to port 443 while HTTPS remains available.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, shell
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 28/100