I found out that this same configuration tested in Firefox has a different output when tested in Chrome.
Dzhalagash Wrote:
-------------------------------------------------------
> server_name www.xn--nicolzanetti-rhb.com xn--nicolzanetti-rhb.com
> www.nicolòzanetti.com nicolòzanetti.com;
> https://www.nicolòzanetti.com -> Works!
> https://nicolòzanetti.com -> Works!
> http://www.nicolòzanetti.com -> Default virtual host and url changed
> to that of default virtual host
> http://nicolòzanetti.com -> Default virtual host and url changed to
> that of default virtual host
https://www.nicolòzanetti.com -> Works!
https://nicolòzanetti.com -> Works!
http://www.nicolòzanetti.com -> Works!
http://nicolòzanetti.com -> Works!
That's weird, maybe Chrome encodes the url differently? What may be a possible explanation? Any way to force Firefox to encode the url the same way Chrome does from the server side perspective?
Dzhalagash Wrote:
-------------------------------------------------------
> server_name www.xn--nicolzanetti-rhb.com xn--nicolzanetti-rhb.com
> www.nicolòzanetti.com nicolòzanetti.com;
> https://www.nicolòzanetti.com -> Works!
> https://nicolòzanetti.com -> Works!
> http://www.nicolòzanetti.com -> Default virtual host and url changed
> to that of default virtual host
> http://nicolòzanetti.com -> Default virtual host and url changed to
> that of default virtual host
https://www.nicolòzanetti.com -> Works!
https://nicolòzanetti.com -> Works!
http://www.nicolòzanetti.com -> Works!
http://nicolòzanetti.com -> Works!
That's weird, maybe Chrome encodes the url differently? What may be a possible explanation? Any way to force Firefox to encode the url the same way Chrome does from the server side perspective?