Gerry Hickman wrote:
I have a SiteCom router with an embedded web server. For many years I was able
to log in
from SeaMonkey by typing http://10.0.0.1/ and then the user name and password.
This still
works in older versions of SM and FF, but not in SM 2.46
I believe the issue is related to a new HTTP header being sent by SM 2.46
Upgrade-Insecure-Requests: 1
I set up a raw HTTP test on a linux VM (without using a browser) and tested
both with and
without this header.
Request with header : Authentication FAILS
Request without header : Authentication WORKS
It's quite strange, as I don't see how the router can even know about this
header as it's
too old. I also noticed something even more odd, if I change the header to
something like
BlahBlahBalh: 1
the authentication also fails, but if I use
BlahBlahBalh: one
everything starts working
Is it possible to disable the 'Upgrade-Insecure-Requests' header in SeaMonkey?
Any references to Insecure in about:config?
_______________________________________________
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey
