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.

Bug 176779 - [68cat] Search result incorrectly flagged
Summary: [68cat] Search result incorrectly flagged
Status: RESOLVED DUPLICATE of bug 176370
Alias: None
Product: www
Classification: Unclassified
Component: Bugzilla (show other bugs)
Version: 6.x
Hardware: PC Windows XP
: P2 normal (vote)
Assignee: leawang
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-11-13 05:35 UTC by Peter Nabbefeld
Modified: 2009-11-18 03:19 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Peter Nabbefeld 2009-11-13 05:35:40 UTC
1. The bug list contains a bug which is already resolved as duplicate.
   Obviously it hasn't been flagged correctly by "meta" tag.
   Only reloading using "Shift+LMB" solves this as a workaround. As this leads
   to viewing incorrect status, this will have negative impact on reviews.
2. Might be related:
   Using latest seamonkey browser. The Html file contains:
   "WARNING: YOUR BROWSER DOESN'T SUPPORT THIS SERVER-PUSH TECHNOLOGY."
   Does bugzilla insist on IE??? This would be a serious problem.
Comment 1 Petr Blaha 2009-11-13 05:45:18 UTC
Hi Peter, is this issue duplicate of bug 176370? There is similar symptoms when non updated pages are returned.
Comment 2 Peter Nabbefeld 2009-11-13 05:58:19 UTC
Yes, You're right. However, please notice the warning in the page's source! This might be a hint, why the caching policy is wrong - probably different templates used to generate the page compared to IE.

*** This bug has been marked as a duplicate of bug 176370 ***
Comment 3 Marco Walther 2009-11-13 12:42:41 UTC
I think that WARNING text serves the same purpose as the similar warning in multipart-mime email messages. It's just there in case the browser does NOT handle multipart-mime.

What basically happens, is
* BZ sends a first mime piece when it starts the work on the query:

WARNING: YOUR BROWSER DOESN'T SUPPORT THIS SERVER-PUSH TECHNOLOGY.
--------- =_aaaaaaaaaa0
Content-Type: text/html; charset=UTF-8

<html>
  <head>
    <title>Bugzilla is pondering your search</title>
  </head>
  <body>
    <h1 style="margin-top: 20%; text-align: center;">Please stand by ...</h1>


  </body>
</html>

* When BZ has the results, it's sending the next mime piece:
--------- =_aaaaaaaaaa0
Content-Type: text/html; charset=UTF-8
content-disposition: inline; filename="bugs-2009-11-13.html"
Set-Cookie: LASTORDER=bugs.bug_status%2Cbugs.priority%2Cmap_assigned_to.login_name%2Cbugs.bug_id; path=/; expires=Fri, 01-Jan-2038 00:00:00 GMT
Set-Cookie: BUGLIST=176490%3A176111%3A176200; path=/; expires=Fri, 01-Jan-2038 00:00:00 GMT

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
                      "http://www.w3.org/TR/html4/loose.dtd">
<html>
  <head>
    <title>Bug List</title>

....
</body>
</html>
--------- =_aaaaaaaaaa0--
WARNING: YOUR BROWSER DOESN'T SUPPORT THIS SERVER-PUSH TECHNOLOGY.

And FF  seems to handle that pretty well. wget seems to be even smarter, it only stores the last mime part.

But for some reason, something is still caching it somewhere for FF. I did not see that in wget or Konqueror.
Comment 4 Marco Walther 2009-11-13 19:44:07 UTC
OK, it was a apache proxy config problem after all. BZ sometimes sends a MIME-type of 'multipart/x-mixed-replace' and that fell into our default expiration setup.

Should be fixed now.