One more TAP question

[Dobos, László]

Hi again,

 

There's a few services which ping-pong the client between http and https by
sending a 302 or 303 when the service url is accessed without https but then
after a POST to /async, the 302 URL is a http://... but sending a GET to it
redirects further to https://. This sort of breaks client logic because if I
turn on automatic redirect follow in the http client library then it gets
redirected even after the first /async POST. But turning on automatic
redirect follow in a client lib is a dangerous thing anyway, especially if
it's running in a server environment.

 

One example to this is the TAP endpoint at
http://www.cadc-ccda.hia-iha.nrc-cnrc.gc.ca/tap/

 

I can again come up with workarounds but specifying in the standard that
redirects should go to the same URL where the POST was sent to would be
better.

 

Cheers,

 

-Laszlo

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.ivoa.net/pipermail/dal/attachments/20180228/7c08c22b/attachment-0001.html>