L
Lennon Day-Reynolds
So, I have an app running a local WEBrick server, which exposes a UI
built in HTML. The HTML contains an iframe which gets refreshed from
Javascript. In IE, this all works flawlessly: I can update the
location of the iframe, it grabs the new content from the 'brick...all
is happy.
In Mozilla (and Firefox), though, things are...less happy. I keep
getting HTTP 400 error codes from WEBrick on the iframe request. The
URLs being requested are exactly the same, and are definitely
(according to the Live HTTP headers plugin, anyway) valid; it's just
something about the Mozilla HTTP request that's freaking WEBrick out.
I know it's not a lot of information to go on, and I'm not really
looking for someone to fix this for me. I'm just trying to see if
anyone else has had problems with Mozilla-based browsers getting HTTP
400 codes off WEBrick for no apparent reason.
built in HTML. The HTML contains an iframe which gets refreshed from
Javascript. In IE, this all works flawlessly: I can update the
location of the iframe, it grabs the new content from the 'brick...all
is happy.
In Mozilla (and Firefox), though, things are...less happy. I keep
getting HTTP 400 error codes from WEBrick on the iframe request. The
URLs being requested are exactly the same, and are definitely
(according to the Live HTTP headers plugin, anyway) valid; it's just
something about the Mozilla HTTP request that's freaking WEBrick out.
I know it's not a lot of information to go on, and I'm not really
looking for someone to fix this for me. I'm just trying to see if
anyone else has had problems with Mozilla-based browsers getting HTTP
400 codes off WEBrick for no apparent reason.