Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

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

Custom HTTP return code instead of 503 #2454

Closed
Prime1Code opened this issue May 17, 2024 · 0 comments
Closed

Custom HTTP return code instead of 503 #2454

Prime1Code opened this issue May 17, 2024 · 0 comments

Comments

@Prime1Code
Copy link

Prime1Code commented May 17, 2024

Is there a docker config to return a custom http code instead / for a 503?

Lets say you have the domain "example.org" with a few subdomains, s1 and s2.

How would you return http 444 in case the user navigates to example.org instead of s1.example.org?

Is there a vhost config or sth similar for this problem? Tried a few options. Nothing worked.

Had to start a separate nginx container serving "nothing" at example.org and then add a vhost config in the nginx-proxy to return a 444.

@Prime1Code Prime1Code changed the title Custom HTTP return code on 503 Custom HTTP return code instead of 503 May 17, 2024
@nginx-proxy nginx-proxy locked and limited conversation to collaborators May 21, 2024
@buchdag buchdag converted this issue into discussion #2458 May 21, 2024

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant