The CDN does some special rewriting to make sure only CDN content is available via the CDN. Perhaps these apache rules didn't get copied from AMO?
Severity: minor → normal
This has something to do with the app. I can reproduce with runserver: # curl -v http://localhost:12999/en-US/firefox/addons/buttons.js?b=6f* About to connect() to localhost port 12999 (#0) * Trying ::1... Connection refused * Trying 127.0.0.1... connected * Connected to localhost (127.0.0.1) port 12999 (#0) > GET /en-US/firefox/addons/buttons.js?b=6f HTTP/1.1 > User-Agent: curl/7.19.7 (x86_64-redhat-linux-gnu) libcurl/7.19.7 NSS/22.214.171.124 zlib/1.2.3 libidn/1.18 libssh2/1.2.2 > Host: localhost:12999 > Accept: */* > * HTTP 1.0, assume close after body < HTTP/1.0 302 FOUND < Date: Mon, 21 Nov 2011 22:54:01 GMT < Server: WSGIServer/0.1 Python/2.6.6 < X-Content-Security-Policy-Report-Only: policy-uri /services/csp/policy?build=6464 < Strict-Transport-Security: max-age=2592000 < Vary: X-Mobile < Location: http://localhost:12999/en-US/firefox/users/login < x-frame-options: DENY < Content-Type: text/html; charset=utf-8 < * Closing connection #0 # ./manage.py runserver 12999 Validating models... 0 errors found Django version 1.4 pre-alpha, using settings 'zamboni.settings_local' Development server is running at http://127.0.0.1:12999/ Quit the server with CONTROL-C. [21/Nov/2011 14:52:23] "GET /en-US/firefox/addons/buttons.js?b=6f HTTP/1.1" 302
Status: NEW → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → FIXED
Component: Server Operations: Web Operations → WebOps: Other
Product: mozilla.org → Infrastructure & Operations
You need to log in before you can comment on or make changes to this bug.