- From: Nicholas Car via GitHub <sysbot+gh@w3.org>
- Date: Mon, 12 Aug 2019 03:26:39 +0000
- To: public-dxwg-wg@w3.org
There seems to be no reason why servers can't include much more information in a redirect header response than they usually do other than expectation/precedence. That is, most documented cases of redirect responses I can find look like this: ``` HTTP/1.1 303 See Other Location: http://example.org/other ``` ...and that's it, but there's nothing preventing: ``` HTTP/1.1 303 See Other Location: http://example.org/other [other headers] ``` e.g.: ``` HTTP/1.1 303 See Other Location: http://example.org/other Content-Profile: http://otherexample.com/profile/x ``` Which would allow the redirecting server to tell the client what profile the resource representation its about to get conforms with. Or any other interesting info like alternative representations `Link` headers. -- GitHub Notification of comment by nicholascar Please view or discuss this issue at https://github.com/w3c/dxwg/issues/1040#issuecomment-520289730 using your GitHub account
Received on Monday, 12 August 2019 03:26:41 UTC