Status: New
Owner: kpreid.switchb.org
Labels: Type-Defect Priority-Medium
New issue 1703 by kpreid.switchb.org: Content-Type of PROXY still wrong
according to Chrome conary
http://code.google.com/p/google-caja/issues/detail?id=1703
Chrome 28.0.1480.0 canary
Caja r5357 with client-side-only changes
Test es53-test-cajajs-invocation.js
From console, broken for readability:
Refused to execute script from '
http://localhost:56901/caja/cajole
?url=http%3A%2F%2Flocalhost%3A56901%2Fant-testlib%2Fcom%2Fgoogle%2Fcaja%2Fplugin%2Fnon-existent-script.js
&input-mime-type=text%2Fjavascript
&transform=PROXY
&callback=caja_ajax_12
&alt=json-in-script
' because its MIME type ('application/json') is not executable, and
strict MIME type checking is enabled.
I thought I fixed this in r5298, but evidently not. We should make sure
that all of our JSONP responses, and this one in particular, are delivered
as text/javascript. Note that the target URL deliberately does not exist.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
--
---
You received this message because you are subscribed to the Google Groups "Google Caja Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.