"GET / HTTP/1.1\" 303
Nobody has claimed this yet.
- Dominant language
- Dockerfile
- Stars
- 1.2k
- Forks
- 1.7k
- PR merge metrics
- No merged PRs in 30d
Description
hola que tal.
estoy haciendo un deployment de odoo en un cluster de kubernetes, y veo que en el log aparece la comprobación de estado 303.
15/Aug/2020 05:39:54] "GET / HTTP/1.1" 303 - 14 0.028 0.304\n"
que es lo que tengo que hacer para que me resuelva con un estado 200?
si yo configuro un LB sobre este workload, este si responde OK!, pero si lo quiero hacer con un "nodeport" el pods en el que esta corriendo resuelve con un estado HTTP 303, en lugar de un HTTP 200:
Contributor guide
No contributing guide indexed for this repository
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
Start by comparing the Kubernetes NodePort and load balancer paths, using the Odoo pod log for GET / as the entry point and checking how each health check is configured. Done means the NodePort path receives the intended health-check response instead of HTTP 303, with the cause and required configuration documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, kubernetes
- Domain
- devops, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100