Fails to deref https schemas, strips https off URL, ignores 301 redirect to https

[n1ywb]

url == //json.readingpl.us/schemas/alertType.json

url SHOULD equal https://json.readingpl.us/schemas/alertType.json

When redirected to HTTPS resource, it instead requests the HTTP resource again

[n1ywb]

I noticed that this behavior does not occur when I serve my app with https.

[JamesMessinger]

This error is caused by the URL resolution logic in the library. It currently defaults to the protocol of the host page, rather than the protocol of the schema URL.

[rickyblaha]

+1

[rickyblaha]

I ended up writing my own resolver. Thanks for the awesome, easy to extend library :)

[big-r81]

Hi,

this is a real problem and you can run into CORS problems too, see #58.
If I debug and adding https in front of the url starting with "//...", the schema is fetched fine...

But I didn't find out, where the protocol is lost... /EDIT: See Fix #59
@BigstickCarpet Can you help?

[JamesMessinger]

This issue was fixed by PR #59 and released in version 4.0.4

[big-r81]

@BigstickCarpet

This issue is only partial fixed.

It won't follow the redirect for me. That still needs to be corrected!

[JamesMessinger]

Oh... I didn't even notice the redirect part of the issue. I thought it was just about the protocol bug.

Let's separate this into two different issues. If the protocol bug is fixed, but the redirect bug is not, then can you create a new issue for just the redirect bug? That'll make things easier to track.