- From: Rob Atkinson via GitHub <sysbot+gh@w3.org>
- Date: Thu, 19 Sep 2019 04:43:39 +0000
- To: public-dxwg-wg@w3.org
Thats a good analysis of an aspect of this issue - I would say that it would be appropriate for the server to respect the query string - and return a response saying that profile is not found. in general I think you are correct if you are saying it would be a misconfiguration to attempt to support negotiation in the http server layer if the application wished to support QSA - the server should be configured to pass those headers to the application - thats certainly the way my implementation will operate. Do you think this needs to be explicitly stated though? It may be worthwhile stating that normal HTTP error responses should be used according to the reason a profile may not be available (including 404 but also access denied etc) - and if really necessary citing this as an example in the precedence section? -- GitHub Notification of comment by rob-metalinkage Please view or discuss this issue at https://github.com/w3c/dxwg/issues/505#issuecomment-532963039 using your GitHub account
Received on Thursday, 19 September 2019 04:43:41 UTC