Skip to main content
Home Forums Silverlight Programming Report a Silverlight Bug HTTP 400 error connecting to Foundry switch UI
9 replies. Latest Post by AllThatJazz on August 5, 2008.
(0)
AllThatJazz
Member
3 points
4 Posts
04-24-2008 9:44 AM |
With Silverlight (1.0, 1.1 or 2.0 beta) installed, I get an HTTP 400 error connecting to the web UI of my Foundry switches. With Silverlight uninstalled, I can connect normally. I've seen a few posts with similar problems, but none concerning Foundry switches so I thought I'd include this to let you know that this seems to be a more widespread problem. Sorry, but I can't/won't deploy Silverlight until this issue is fixed.
Yi-Lun L...
All-Star
25052 points
2,747 Posts
04-28-2008 4:36 AM |
Hello, this is unlikely to be a Silverlight problem. Silverlight is a browser plug-in. It has nothing to do with switches. Try to disable the Silverlight plug-in without uninstalling and see if the problem gets away. If the problem persists, feel free to let us know.
04-30-2008 1:47 PM |
I tried disabling the plugin, but the problem persists. Uninstalling Silverlight is the only thing that allows me to log in to the switch using the web UI via IE7.
As I stated in the original post, the problem is in connecting to the web based user interface of the switch, so saying "it has nothing to do with switches" just shows me that you aren't reading the full post. The browser most certanly does have something to do with accessing a web based UI! I have found some posts relating to similar problems with HP switches and d-Link devices, so maybe there is a wider problem here.
BTW, I've re-run all my tests with Firefox as the browser and Silverlight installed, and have had no problems connecting to the switches. Maybe it's an IE7 thing?
tcordes
6 points
3 Posts
06-14-2008 2:34 PM |
See http://silverlight.net/forums/t/7452.aspx same problem?
06-17-2008 9:08 AM |
Yup. That seems to be a similar issue. I'll post over there from now on. Do you know if MSFT has even acknowledeged this as a problem? Last official word I got was that it was "unlikely to be a Silverlight problem", then silence.
06-17-2008 1:18 PM |
I don't see anyone from MS replying on the topic, and no MSKB entry yet from what I can find. Start making a stink on the other thread. Isn't this forum supposed to have MS people watching it?
It's easy to see it's a Silverlight problem. Install SL, page breaks. Uninstall SL, page works. Use FF, page works. Can't argue with that logic!
06-17-2008 11:14 PM |
Hi, we're investigating this issue...
MBP
4 points
2 Posts
08-05-2008 1:12 PM |
Same problem here but discovered that a registry entry length was the cause.
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Internet Settings\Accepted Documents
Make sure the above entries do not combine to exceed 299 chars. (at least for my DLINK device)
When it was at 300 chars or more got error 400.
When I changed it to 299 or less chars DLINK web interface worked fine.
I guess most people are installing Silverlight and this is one of the few apps that actually modify this registry entry.
coryb891
14 points
08-05-2008 1:37 PM |
Expanding on the previous post (MPB and I both worked on this issue)...
Our device is a DLink DCS-2100. The problem is apparently due to a buffer overflow isssue on the camera. The problem is with the "Accepts" header line in the request. In my browser, the header looks like the following:
Accept: image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, application/x-ms-application, application/vnd.ms-xpsdocument, application/xaml+xml, application/x-ms-xbap, application/vnd.ms-excel, application/vnd.ms-powerpoint, application/msword, application/x-shockwave-flash, application/x-silverlight, */*
I connected to the camera using telnet and pasted the request and received the 400 error. But if I reduce the length of the Accepts header by 8 characters (or say remove the application/x-silverlight entry) and paste this into telnet, I receive a normal response. The device cannot handle header lines longer than 298 characters (or 300 including the CRLF).
The workaround is to simply remove one of these entries. This can be done by removing one of the registry values located at the key that MBP posted. If you are using 32-bit IE on 64-bit windows, you will need to delete a value from
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Internet Settings\Accepted Documents
Hope this helps to solve your problem as well.
08-05-2008 2:26 PM |
WOW, good sleuthing!
I just tried this and it works as advertised. (once I realized that I had to include the "Accept: " in the 298 word maximum) I deleted two of the entries, for x-ms-application and vnd.ms-xpsdocument and was able to get to the web UI without any problem.
I'm going to forward this to Foundry so they know what's going on, too
Thanks again!
HTTP 400 error connecting to Foundry switch UI