Wireshark-bugs: [Wireshark-bugs] [Bug 7586] Incorrect content-type for non-optimized javascript
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Sun, 12 Aug 2012 12:01:55 -0700 (PDT)
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=7586

Gerald Combs <gerald@xxxxxxxxxxxxx> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |LATER

--- Comment #3 from Gerald Combs <gerald@xxxxxxxxxxxxx> 2012-08-12 12:01:55 PDT ---
Is text/javascript showing up in any HTTP response headers? If so that's a bug
either I or the Stingray[1] team need to fix. If they're showing up inside
<script/> tags then that's because it's "required in order to function properly
for a large number of our visitors" instead of "obsolete", despite what RFC
4329 might say:

http://stackoverflow.com/questions/1288263/why-doesnt-ie8-recognize-type-application-javascript-in-a-script-tag

http://stackoverflow.com/questions/876561/when-serving-javascript-files-is-it-better-to-use-the-application-javascript-or


[1] www.wireshark.org is currently behind a Stingray Traffic Manager. You can
disable and reenable optimization by appending "?aptimizer=off" and
"?aptimizer=on" to your URL.


Marking it as RESOLVED/LATER. It appears that IE 9 and above support
application/javascript so we just need to wait for the browser market share to
change.

-- 
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.