Support for relative URLs in Location header #23385
Labels
customer-reported
Issues that are reported by GitHub users external to the Azure organization.
needs-triage
Workflow: This is a new issue that needs to be triaged to the appropriate team.
question
The issue doesn't require a change to the product in order to be resolved. Most issues start as that
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: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.The text was updated successfully, but these errors were encountered: