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

Missing /etc/mime.types #10309

Closed
lucasfcnunes opened this issue Aug 13, 2023 · 1 comment · Fixed by #10310
Closed

Missing /etc/mime.types #10309

lucasfcnunes opened this issue Aug 13, 2023 · 1 comment · Fixed by #10310
Labels
kind/bug Categorizes issue or PR as related to a bug. needs-priority needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.

Comments

@lucasfcnunes
Copy link
Contributor

As @mrksngl stated in 2021 /etc/mime.types is not present in the latest image (#7728 (comment)).

registry.k8s.io/ingress-nginx/nginx-errors:v20230404-helm-chart-4.6.0-11-gc76179c04 @ https://console.cloud.google.com/gcr/images/k8s-artifacts-prod/us/ingress-nginx/nginx-errors
image

Impact on e.g. curl --request GET --url http://localhost:8080/ --header 'X-Format: application/rss+xml'

with /etc/mime.types

unexpected error opening file: open /www/404.rss: no such file or directory
unexpected error opening file: open /www/4xx.rss: no such file or directory
http: superfluous response.WriteHeader call from main.errorHandler.func1 (main.go:164)

without mime /etc/mime.types

couldn't get media type extension. Using .htm
unexpected error reading return code: strconv.Atoi: parsing "": invalid syntax. Using 404
serving custom error response for code 404 and format application/rss+xml from file /www/404.html
@lucasfcnunes lucasfcnunes added the kind/bug Categorizes issue or PR as related to a bug. label Aug 13, 2023
@k8s-ci-robot
Copy link
Contributor

This issue is currently awaiting triage.

If Ingress contributors determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@k8s-ci-robot k8s-ci-robot added needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. needs-priority labels Aug 13, 2023
lucasfcnunes added a commit to lucasfcnunes/ingress-nginx that referenced this issue Aug 13, 2023
lucasfcnunes added a commit to lucasfcnunes/ingress-nginx that referenced this issue Aug 13, 2023
Signed-off-by: Lucas Fernando Cardoso Nunes <[email protected]>
k8s-ci-robot pushed a commit that referenced this issue Aug 13, 2023
Signed-off-by: Lucas Fernando Cardoso Nunes <[email protected]>
k8s-infra-cherrypick-robot pushed a commit to k8s-infra-cherrypick-robot/ingress-nginx that referenced this issue Sep 7, 2023
Signed-off-by: Lucas Fernando Cardoso Nunes <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug. needs-priority needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.
Projects
Archived in project
2 participants