This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
This is starting to be quite annoying. From time to time it happens that the result of the query is not a correct HTML source. Therefore it's displayed in the browser as a plain text - the HTML is not interpreted. My query is: http://www.netbeans.org/issues/buglist.cgi?resort=1&Submit%20query=Submit%20query&issue_type=DEFECT&component=debuggercore&component=debuggerjpda&subcomponent=code&subcomponent=documentation&subcomponent=graphics&subcomponent=ui&subcomponent=www&issue_status=UNCONFIRMED&issue_status=NEW&issue_status=STARTED&issue_status=REOPENED&email1=&emailtype1=substring&emailassigned_to1=1&email2=&emailtype2=substring&emailreporter2=1&issueidtype=include&issue_id=&changedin=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&short_desc=&short_desc_type=substring&long_desc=&long_desc_type=substring&issue_file_loc=&issue_file_loc_type=substring&status_whiteboard=&status_whiteboard_type=substring&keywords=&keywords_type=anytokens&field0-0-0=noop&type0-0-0=noop&value0-0-0=&order=issues.priority%2C%20issues.issue_id The result is attached.
Created attachment 25539 [details] The bad "HTML" file.
I have not experienced this ... Martin, can you include details of your browser/OS, in case they are relevant ? Thanks.
Mozilla 1.4.1, Linux Fedora Core 1 on x86 (Intel Centrino). It worked fine since cca 1 hour after I've submitted this issue. Now it happens again. It's random.
I wonder if this is related to the server going down and/or returning 500 errors ... ?
Have no idea. Anyway, the problems with IZ server have a considerable impact on our work.
Hello, Well, I cannot reproduce this, althought the HTML file is definitely wrong. If you are behind another cache server then I would definitely request that you investigate that setup. I am not aware of any other user reporting this issue.
Hello Mentlicher, Can you please add the Live HTTP header to your Mozilla/FF browser and attach the captured headers when you run into this problem next? Thanks
We recently moved out from Collabnet's infrastructure