Thanks Dennis,
>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
Thanks Pascal,
I try it as well with :
return new WOResponse(); // supposed to be 200 OK
But Google Wallet rejects is the same way
Pierre
Le 19. 09. 14 10:10, Pascal Robert a écrit :
Why aren't you using WOResponse instead of your custom class?
Envoyé de mon iPhone
Le 2014-09-19 à 03:1
Why aren't you using WOResponse instead of your custom class?
Envoyé de mon iPhone
> Le 2014-09-19 à 03:12, Pierre Gilquin a écrit :
>
> Hi WO people,
>
>
> I try to send a 200 OK response with this code from WOPaypal framework
>
>
>private static class HTTPStatusResponse extends WOResp
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 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
Hi WO people,
I try to send a 200 OK response with this code from WOPaypal framework
private static class HTTPStatusResponse extends WOResponse {
public static void setResponse( WOResponse response, int
statusInt, String statusString ) {
String contentString = "HTTP/1
