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

Better support for error pages #3840

Open
drspangle opened this issue Jun 29, 2024 · 0 comments
Open

Better support for error pages #3840

drspangle opened this issue Jun 29, 2024 · 0 comments

Comments

@drspangle
Copy link

Is your feature request related to a problem? Please describe.

Right now, when a server that is being proxied via NPM isn't yet available, a 502 "bad gateway" error is returned. This is fine, it's the expected behavior, but it would be a lot nicer if it were possible to instead redirect to a nicer error page. This would be especially helpful if that page could include javascript to redirect back to the original page after a time, allowing services to come online (obviously this custom page would be written by the end user).

Describe the solution you'd like

I'd like to be able to specify the error pages for handling various errors, in particular 502. You should be able to go into a domain's settings and specify the redirection URL, and/or specify a custom static HTML file to use.

Describe alternatives you've considered

The only real alternative here is to manually edit the nginx config inside the container, which there is lots of documentation to show is possible, but that defeats the purpose of using NPM.

Additional context

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant