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.
Created attachment 145591 [details] response body In Internet Explorer 11, when clicking the link https://netbeans.org/bugzilla/buglist.cgi?bug_status=NEW&bug_status=STARTED&bug_status=REOPENED&emailassigned_to1=1&emailreporter1=1&emailtype1=exact&email1=c69%40netbeans.org&field0-0-0=bug_status&type0-0-0=notequals&value0-0-0=UNCONFIRMED&field0-0-1=reporter&type0-0-1=equals&value0-0-1=c69%40netbeans.org i get the "do you want to save or open this file ?" dialog This makes it almost impossible to use bug tracker in a default Win7/Win8 browser. ____ Response headers: Key Value Response HTTP/1.1 200 OK Date Wed, 26 Feb 2014 00:54:36 GMT Server Apache/2.2.24 (Unix) mod_perl/2.0.7 Perl/v5.14.2 X-xss-protection 1; mode=block X-frame-options SAMEORIGIN X-content-type-options nosniff Content-Type multipart/x-mixed-replace;boundary="------- =_i26rp1BwryxNV6b09"; charset=UTF-8 Cache-Control max-age=2592000 Expires Fri, 28 Mar 2014 00:54:36 GMT Keep-Alive timeout=5, max=99 Connection Keep-Alive Transfer-Encoding chunked
Did you play with the browser's user agent string? Bugzilla knows that it should not use the `serverpush' for MSIE. So I'm somewhat at a loss why your IE would get that response:-( From the BZ code: "# Server push is compatible with Gecko-based browsers and Opera, but not with # MSIE, Lynx or Safari (bug 441496). my $serverpush = $format->{'extension'} eq "html" && exists $ENV{'HTTP_USER_AGENT'} && $ENV{'HTTP_USER_AGENT'} =~ /(Mozilla.[3-9]|Opera)/ && $ENV{'HTTP_USER_AGENT'} !~ /compatible/i && $ENV{'HTTP_USER_AGENT'} !~ /WebKit/ && !defined($cgi->param('serverpush')) || $cgi->param('serverpush'); "
IE11 has different user agent, which confuses old scripts: for example here is the one on Win8.1: Mozilla/5.0 (Windows NT 6.3; WOW64; Trident/7.0; Touch; MASMJS; rv:11.0) like Gecko
see MSDN: http://msdn.microsoft.com/en-us/library/ie/bg182625.aspx#uaString
We are in the process to update BZ to 4.4.2. That will also fix this problem.
While exploring other issue #242866 I encounter a similar issue I found a bug[1] related to this I guess. https://bugzilla.mozilla.org/show_bug.cgi?id=902515 In anticipation thanks for the planned update.