you can use a .htaccess file to solve that: in your .htaccess add
AddType text/javascript .js http://httpd.apache.org/docs/2.2/mod/mod_mime.html#addtype On Wed, May 5, 2010 at 11:53 AM, menoz <[email protected]> wrote: > I found that the headers sent by google and my server are really > different (only the significant headers are reported): > > - downloading from google: > Content-Type text/javascript; charset=UTF-8 > Vary Accept-Encoding > X-Content-Type-Options nosniff > Server sffe > Content-Encoding gzip > > - downloading from my server: > Content-Type application/x-javascript > (none of the above headers are present, only this is sent) > > So, it is clear that is a header related problem, but the question is: > how can I add these headers? I'm working on Zend, but to be honest I > do not really know where to set these headers for a specific > (javascript) file.. > Have you got any ideas? > > Bye, > Daniele > > > On 5 Mag, 09:48, Peter Duncanson <[email protected]> > wrote: > > Firebugs net panel will be able to tell you all you need. > > > > Sent from my iPhone > > > > On 5 May 2010, at 08:24, menoz <[email protected]> wrote: > > > > > I downloaded the 1.2.0 version from this link: > > >http://mootools.net/download/get/mootools-1.2-core-yc.js > > > > > Even if I "solved" the problem directly downloading the core code from > > > google, I would like to understand what the real problem is, so: can > > > you please tell me how can I see what MIME type is server by the > > > server, and maybe understand if that is the problem? > > > Can Firebug be useful in this case, or do I need a more complex > > > software? > > > > > Thank you all very much, > > > Daniele > > > > > ps: I also tried to remove the hex# from 1.2.1+ but that didn't solve > > > the problem. > > > > > On 4 Mag, 21:07, Sanford Whiteman <[email protected]> wrote: > > >>> If it works, then it *may* be something wrong with the MooTools > > >>> server. Otherwise, I'd assume your network is misinterpreting the > > >>> file > > >>> as binary, or something related that confuses it with a harmful > > >>> file. > > > > >> +1 > > > > >> 512B sounds like an IPS/firewall is trying to do some MIME > > >> type > > >> pre-sniffing and determining that it isn't valid text/plain (note > > >> that > > >> is the MIME type served by mootools.net, I presume to > > >> facilitate > > >> downloading as an attachment as opposed to using the main site as > > >> your > > >> CDN). > > > > >> 1.2.0 (I don't know where exactly you are getting it from > > >> on > > >> mootools.net) may be getting served as application/x-javascript, > > >> since > > >> it is actively used to power the site + demos. This one may be > > >> sniffed > > >> according to different IPS rules. > > > > >> Another diff is that 1.2.1+ has a long hex build # at the > > >> beginning, > > >> which maybe is nonmatching with text/plain. Just a guess there. > > > > >> -- S. > -- http://tbela99.blogspot.com/ fax : (+33) 08 26 51 94 51
