Ken,
I'm guessing that you were using IIS on your XP laptop. I don't use IIS
in any capacity (for my own sanity), but I can tell you that Apache has
a MIME magic module (assuming it's loaded in the Apache configuration,
which it is by default) that controls the header that gets sent for
various file types. The settings for the MIME magic module is managed
through one of the Apache conf files, which varies by the specific
Apache build, so you might try tweaking ("sharp twisting motion") the
mime type setting for Javascript content to try to send the app/js
header instead of the application/javascript header to see what effect
it has. You could even try sending the application/x-javascript header
to see if it reproduces the problem on Apache, in case the problem is
really caused by some other difference between the two web servers.
This problem is likely impacted by how the various browsers interpret
each mime type value, but it would be really surprising (or not) to
learn that IIS sends a mime type header that IE doesn't recognize!
Maybe IIS has a similar capability for mime type headers, but I couldn't
tell you myself.
HTH,
Gene
On Wed, 2009-10-07 at 11:00 -0400, Ken MacDonald wrote:
> Thanks for that, Gene! Oh well. OK, we do have another data point in
> the IE6 mystery: we moved the app to a server running Apache, and it
> seems to work fine with IE 6 there. We looked at the headers being
> passed back from my dev server when <myappname>.js was served, and
> then at the headers from the Apache server, and found the "Content-
> Type" was "application/javascript" on Apache, "application/x-
> javascript" from my dev server where it fails. I've grep'd a ton of
> code to see if i can find if this is being set explicitly somewhere
> that we could hack and try to see if it would help, but didn't find
> anything, so I'm a bit puzzled what the difference is between
> javascript and x-javascript, why IE6 should care, and how to see if we
> could change the headers to plain app/js.
> Ken
>
> On Tue, Oct 6, 2009 at 4:25 PM, Gene Amtower <[email protected]>
> wrote:
>
> On Tue, 2009-10-06 at 15:55 -0400, Ken MacDonald wrote:
>
> > FYI, I don't think I mentioned it before, but this problem
> > occurs in both the build and source versions of the
> > application.
> >
> > Something else interesting - I got a brand-new laptop when I
> > started here in August. Came with Windows XP - SP3. And IE
> > 6. I'd have thought a new computer would come with a more
> > recent version of IE.
>
>
>
> Ha-ha, Ken. That's sort of funny! New computer, but old
> operating system. The current XP SP3 OEM install is the
> original SP3 release from some years ago, and the OEM versions
> are a fixed-point in time - they don't get updated over time.
> Consider yourself lucky that you could still get XP
>
>
> ------------------------------------------------------------------------------
> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart your
> developing skills, take BlackBerry mobile applications to market and stay
> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
> http://p.sf.net/sfu/devconference
> _______________________________________________ qooxdoo-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
