What we need is more information from someone who _is_ experiencing the problem, or maybe someone with the same Linksys model and using Firefox who isn't so we can start teasing apart differences.ĭavid C. Ross who is not experiencing this bug and is using a different browser and router from the person who reported it. I am not asking for information from David E. I assume that since versions 47.0.2 and 48.0 of Firefox (where it worked/broke) both made request headers, some corruption got in 48.0 - id/password got copied an maybe overflowed some array of something. My login id is 'admin' (no quotes) with a 12 character password. Perhaps you could reproduce this problem if you could fine a similar behavior for something that causes a pop up login window. So I'm thinking that perhaps something is going on that corrupts the transfer from the popup login window to the request header (if that contains the login info). Normally a login process presents a page with a form for login/password - NOT a popup window. The problem is that the pop up window for the router login seems to get in the way of seeing any request/response network dialog - hence my delay for a "period of thinking". I tried to get Chrome and Firefox request and response headers, but no luck using "inspect element" for the page. Can you check the request headers for Chrome and Edge when connecting to your router?īeen thinking about this for awhile and trying things.Īnother browser works just fine: OPERA 43.0
Maybe it does not send it for all top level loads as Firefox does. So for regular pages, that means Chrome also sends the upgrade-insecure-requests header. > Accept: text/html,application/xhtml+xml,application/xml q=0.9,image/webp,*/* q=0.8
Linksys wrt120n reset button not working mac os x#
> User-Agent: Mozilla/5.0 (Macintosh Intel Mac OS X 10_12_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/.87 Safari/537.36 > Accept: text/html,application/xhtml+xml,application/xml q=0.9,*/* q=0.8
Christoph: It's not just Chrome that works it's Microsoft Edge too.
0 kommentar(er)
