fix bug when respec is referenced using https

[cconcolato]

No description provided.

[tobie]

This is breaking the build. Not sure why.

You might want to give //specref.jit.su/bibrefs?... a try instead.

[cconcolato]

Sorry, I could not test the build. I couldn't find the documentation...
It is strange though that it doesn't work, the file header says "respecConfig" is a global variable. Maybe it is unassigned at that time.
Using // could work, but I've been told it does not work with "file:" so I wouldn't be able to test locally.

[cconcolato]

Ok I just discovered Travis-CI for respec: https://travis-ci.org/darobin/respec
I don't understand the errors though...

[tobie]

Yup, looks like I need to fix the test runner.

[darobin]

respecConfig is global as an external interface, i.e. the page that is including ReSpec can modify it multiple times (since that can be convenient) and expect reasonable results. But inside the code, there's no need to use it as each plugin gets a conf object passed in.

That said, I don't think that that's the issue that's breaking the build. Let me dig further.

[darobin]

@cconcolato didn't break the build, I did!

[darobin]

For future reference, I found what the bug was.

conf.scheme reflects the currently used scheme. That's useful in some cases, but not when trying to reference something on the Web in an HTTPS-friendly manner. When running in many cases, it'll be fine, but for instance the test suite exercises more exotic situations and those break.

conf.httpScheme will give you https if on https, and http otherwise. That's the one to use. (Fix applied and shipped)

Thanks!