meektechie
meektechie
Yes You are right, We are looking to catch all when no hostnaes or paths match. We just want to add a custom error page/html file instead of the default...
Thanks for sharing this, I already went through this. I need to apply a custom response for the 404 page but the custom response always goes to 302.
With this page, i want to cusomize. 400 The plain HTTP request was sent to HTTPS port 400 Bad Request The plain HTTP request was sent to HTTPS port nginx
Nope, it isn't working
Awesome, It works well. Is it possible to use multiple domains here?.
Thanks Zeritti. I have been seeking the support for the couple of weeks.
How can i raise a request to enable this feature?