HTTPS is modified to the HTTP troubleshooting process

through nginx Proxy, send the request to the back-end Tomcat Server, and the requested information is passed to the back-end server:

Proxy_http_version 1.1;

Proxy_set_header Connection "";

Proxy_set_header Host $host;

Proxy_set_header X-real-ip $remote _addr;

Proxy_set_header x-forwarded-for$proxy_add_x_forwarded_for;

because the back-end program in the jump when the use of automatic jump (no longer the page to send requests), resulting in jump failure, in the browser development tool can be seen to be limited because the browser is using the HTTPS protocol, but received the return of HTTP, to intercept it. (only provide the way to view, the specific error is not recorded)

650) this.width=650; "Src=" Http://s4.51cto.com/wyfs02/M00/85/24/wKioL1ea68KB5BIhAADfTxI1yNE604.png-wh_500x0-wm_3 -wmp_4-s_3043158256.png "style=" float:right; "title=" 1.png "alt=" Wkiol1ea68kb5bihaadftxi1yne604.png-wh_50 "/>

Finally, the reason is that the development of colleagues in the write jump code assembly path is, by mistake, the HTTPS protocol interception, resulting in the assembled path is the HTTP protocol, blocked by the browser. The specific workaround is to add the following in the relevant method:

<propertyname= "Redirecthttp10compatible" value= "false"/>

Troubleshooting tips:

1. You can see the specific error reasonthrough the development tool's console bar, very good.

This article is from the "Operation and maintenance of the Road" blog, please be sure to keep this source http://lrtao2010.blog.51cto.com/10425744/1831669

HTTPS is modified to the HTTP troubleshooting process