Support for relative URLs in Location header

[thomas11]

Feature Request

The HTTP Semantics RFC shows that URLs in the Location header can be relative, and the client should turn them into absolute URLs by adding the relevant path:

For example, a GET request generated for the URI reference "http://www.example.org/~tim" might result in a 303 (See Other) response containing the header field:
Location: /People.html#tim
which suggests that the user agent redirect to "http://www.example.org/People.html#tim"

Where as the poller implementation explicitly asserts that the URL is absolute.

To fully support the RFC, handling relative Locations would be required.

I ran into this issue once with an Azure service returning a relative Location, but unfortunately didn't capture the error at the time.

[jhendrixMSFT]

Do you know which Azure service returned the relative URL? For ARM services, it's required that URLs for polling are absolute (see Azure RPC spec).

[thomas11]

I don't, unfortunately. I'll see if I can repro it again.

Good to know that absolute URLs are required, so the relative URL - if I didn't mess up on my part - was a rare exception.