Closed
Bug 716376
Opened 14 years ago
Closed 14 years ago
unable to log on to a web based device
Categories
(Firefox :: Untriaged, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: m.huinink, Unassigned)
Details
Attachments
(1 file)
401.09 KB,
application/octet-stream
|
Details |
User Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:12.0a1) Gecko/20120107 Firefox/12.0a1
Build ID: 20120107031040
Steps to reproduce:
Try to log on with firefox 9.0.1 to a webbased configuration tool of an adsl 2+ modem from a windows 7 machine 64 bit.
Actual results:
Entering the address of the device 10.0.0.1 a login screen appears. After entering username and password and sending it to the device an empty login screen appears again. Canceling the log on an error appears:401 Authorization Required
Browser not authentication-capable or authentication failed.
Expected results:
I should have been connected to the configuration tool of the adsl2+ modem.
Comment 2•14 years ago
|
||
Have you enabled the "Do not track" feature ?
(alt key)/tools/options/privacy/Tell websites I do not want to be tracked
Some embed devices seem to have a broken http server that fails with this http header.
The do not track option was enabled. Disabling this option made it possible to log on to the device. The same with Firefox on windows xp. With the no track option enabled impossible to log on.
But isn't there a possibility to detect if your dealing with an internet website or a browser-based configuration tool. Now the no track option must be disabled whenever you want to use a browser-based application on a device to do whatever is needed and enable the now track option after you finished using the browser-based application. There should not be any restriction in using firefox, meaning that firefox should be able to detect if your dealing with an webbased application on the internet or on a device.
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → INVALID
Comment 4•14 years ago
|
||
This broken webserver is only known from one linksys router and nor from your ADSL device which is probably also build by linksys.
The DNT feature only adds a HTTP Header in the request and it's unbelievable that a webserver fails with this header.
We could disable that header for private IPs but we would then get bug reports from developers who are developing their sites and want to test the DNT feature.
The adsl device is a sitecom adsl 2+ chinese make. Made in china for linksys?
I have another router linksys and this router is reachable with the no tracking option enabled.
Ok thanks for your help.
Resolution: INVALID → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•