workaround to handle HTTP and HTTPS on same port?

Nader Ziada nziada at pivotal.io
Wed Oct 18 15:54:50 UTC 2017


Hi,

In order to support HTTP and HTTPS on the same port we had to enable SSL
for that listen port in the nginx config and remap the 497 nginx error code
to a permanent redirect. To be transparent to the client making the request
(written in go), we used "error_page 497 301 =200 $request_uri;".

This seems to work for the GET requests, but not for PUT requests.

This is a temporary workaround that we need while the more permanent
solution is being worked on, so we're wondering if anybody here had any
workarounds or tips on how to achieve that.

Thanks!
Nader
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nginx.org/pipermail/nginx/attachments/20171018/94e55640/attachment.html>


More information about the nginx mailing list