[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: FW: [xrds-simple] X-XRDS-Location and redirects
This question was just asked on the XRDS-Simple list, and it was good enough I though it needed scrutiny here as well. =Drummond -----Original Message----- From: xrds-simple@googlegroups.com [mailto:xrds-simple@googlegroups.com] On Behalf Of Manger, James H Sent: Wednesday, April 02, 2008 10:46 PM To: xrds-simple@googlegroups.com Subject: [xrds-simple] X-XRDS-Location and redirects Q. Do HTTP redirects or an X-XRDS-Location header take precedence? Phrased differently, what should a client do after the following discovery request & response? -> GET /some/resource HTTP/1.1 Host: example.org Accept: application/xrds+xml <- 303 See Other X-XRDS-Location: http://example.org/some/resource.xrds Location: http://example.org/some/resource.html Option 1: follow X-XRDS-Location -> GET /some/resource.xrds HTTP/1.1 Option 2: follow HTTP redirect -> GET /some/resource.html HTTP/1.1 I don't think the specs (XRDS or XRDS-Simple) indicates which option is right, or whether the client is free to choose. I prefer option 1 -- probably as allowed client behaviour, or perhaps as required behaviour. Whatever the choice, it would be good to explicitly state it in the spec. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "XRDS-Simple" group. To post to this group, send email to xrds-simple@googlegroups.com To unsubscribe from this group, send email to xrds-simple-unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/xrds-simple?hl=en -~----------~----~----~----~------~----~------~--~---
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]