What's going on is that when Mozilla attempts to load http://hip.unmc.edu/js/enum.js, it gets back "<HTML><HEAD><TITLE>304 Not modified</TITLE></HEAD>..." prepended to the contents of the .js file. I don't know why that's happening--could it be an error in our networking code? Neither 4.x or IE have the problem.
Assignee: norris → gagan
Component: DOM Level 0 → Networking
QA Contact: cbegle → tever
Hmmm... interesting, a trace on 4.7 shows two requests for the same .js file but only one response. Since 304 means we did a If-Modified-Since, we are probably not patching the response back correctly. cc'ing cache guys.
cc'ing with more force... :) ->gordon
Assignee: gagan → gordon
The problem may be related to the fact that mozilla doesn't update the URL it's viewing when it recieves a 304. This is Bad. If you reload once the page is loaded, then the correct URL is shown. To view for yourself, follow any applications homepage/changelog/download type link at http://freshmeat.net - they all use freakin 304s...
Moving post beta bugs to M18 which is now the post-beta milestone.
Target Milestone: M17 → M18
need more info on if this is still happening.
no info as yet. and too late.
Whiteboard: [NEED INFO] → [NEED INFO][nsbeta3-]
worksforme under Mac OS 9.0.4, so must be WinNT bug. mozilla build 2000092804-M18.
Finally tried Netscape 6 No Joy.
Still not fixed with the new cache. We'll need to investigate for 0.9.1.
Target Milestone: mozilla0.9 → mozilla0.9.1
This is more likely to be a problem with HTTP than the cache. Darin, what do you think?
Assignee: gordon → darin
Component: Networking → Networking: HTTP
neeti: do you think you could help investigate this bug? are we still seeing this error in recent builds? thanks!
Status: NEW → ASSIGNED
this appears to be fixed now.
Status: ASSIGNED → RESOLVED
Last Resolved: 18 years ago
Resolution: --- → WORKSFORME
I can't connect to that url - eventually the connection just times out.
the server just appears to be down.
Status: RESOLVED → VERIFIED
QA Contact: tever → junruh
You need to log in before you can comment on or make changes to this bug.