Not respecting HTTP 301 to a HTTPS URL

[Andrew Langhorn]

Hi,

I'm calling some Javascript in a Mustache template using the HTML src tag from an external source, using an absolute URL. The remote returns a HTTP 301 with a Location header because the request was performed by PhantomJS over HTTP, and we only support HTTPS on our assets servers.

Is it a known thing that PhantomJS won't respond properly when presented with a HTTP 301 response with a Location header pointing to a HTTPS URL?

Thanks,

Andrew

--

Andrew Langhorn
Senior Site Reliability Engineer
Email	andrew....@thoughtworks.com