Hi, I think you shouldn’t need to add the HTTP header on your own, WO already does that for you.
On 19.09.2014, at 09:12, Pierre Gilquin <[email protected]> wrote: > The answer is > HTTP/1.1 200 Apple > instead of OK ! > > Can that be the problem and how can I change that ? In theory a correct implementation of the standard shouldn’t mind (http://www.w3.org/Protocols/rfc2616/rfc2616-sec6.html#sec6.1): > The Status-Code element is a 3-digit integer result code of the attempt to > understand and satisfy the request. These codes are fully defined in section > 10. The Reason-Phrase is intended to give a short textual description of the > Status-Code. The Status-Code is intended for use by automata and the > Reason-Phrase is intended for the human user. The client is not required to > examine or display the Reason- Phrase. > and further down > The individual values of the numeric status codes defined for HTTP/1.1, and > an example set of corresponding Reason-Phrase's, are presented below. The > reason phrases listed here are only recommendations -- they MAY be replaced > by local equivalents without affecting the protocol. So clients should never care about the textual response part and you should be good, just the status code (which should be valid for Google Wallet as well). Of course in practice there are (as with most web protocols these days) implementations, that do not fully adhere to the standards… Maybe your issue arises, because you also add the string “HTTP/1.0 200 OK” to the actual response content body? Greetings Dennis
_______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [email protected]
