gbif / validurl-ws

validurl-ws

Please note this project is used exclusively by the IPT

The validurl-ws provides:

• A web service to validate if a URL is publicly availalbe or not. The IPT calls this web service before registration with GBIF, e.g. http://tools.gbif.org/ws-validurl/?url=http://ipt.gbif.org/&callback=?

To build the project

mvn clean install

Policies

• This project is and should be used exclusively by the IPT

validurl-ws's Issues

Serve tools.gbif.org/ws-validurl with HTTPS

During IPT registration, the IPT calls http://tools.gbif.org/ws-validurl to validate its base URL.

Unfortunately, when the IPT is served with HTTPS this call will generate a Blocked loading mixed active content error (see screenshot below).

To fix this problem, we should serve tools.gbif.org/ws-validurl with HTTPS.

For backwards compatibility, requests using HTTP (coming from older versions of the IPT) should still be supported and redirect to HTTP.

Until tools.gbif.org/ws-validurl can be served with HTTPS, new IPTs installed with HTTPS cannot be registered unless the user disables protection on the page (a browser setting), although this is not recommended for obvious reasons.

For the workaround described above to work, IPT v2.3.3 must still make the request with HTTP. Assuming this issue gets fixes, later versions of the IPT can switch to using a protocol-agnostic URL for the call.