The plain HTTP request was sent to HTTPS port

[Ilan Berkner]

I've come across this setting for nginx, but am not sure if this will solve
it?

  proxy_set_header X_FORWARDED_PROTO https;



2009/8/21 Igor Sysoev <is at rambler-co.ru>

> On Thu, Aug 20, 2009 at 09:05:18PM -0400, Ilan Berkner wrote:
>
> > So we're doing a credit card transaction and it comes back from paypal on
> > the return trip with that error (on our end).  The reason is that the
> return
> > URL is:
> >
> > http://www.domain.com:443/....
> >
> > so its trying to access port 443 via http.
> >
> > I won't know till tomorrow, but I hope that we can adjust the return URL
> to
> > correctly be "https://www.domain.com... than it works as it should.
> >
> > My question is, should I put something in the Nginx configuration file
> that
> > if someone tries to access "http" using port 443, redirect them to https?
> > If so, how?  Is that the correct way of going about it outside of
> correcting
> > the return URL (which of course would be the ideal way), but in general,
> > should requests coming to http://www.domain.com:443 be forced to HTTPS?
>
> nginx supports some internal error codes to handle error_page redirection:
>
>     error_page  497  https://$host$request_uri;
>
> 497 means that plain HTTP request was sent to HTTPS port.
>
>
> --
> Igor Sysoev
> http://sysoev.ru/en/
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://nginx.org/pipermail/nginx/attachments/20090821/9cc80bc7/attachment.html>