Re: WOResponse 200 OK

2014-09-19 Thread Pierre Gilquin

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 standards…


I think i have to wait for answer from GW forum


>Maybe your issue arises, because you also add the string “HTTP/1.0 200 
OK” to the actual response content body?


I did remove the line  as well as  the simplest "return new WOResponse();"
but GW don't like it !




___
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list  (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: WOResponse 200 OK

2014-09-19 Thread Pierre Gilquin

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: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 WOResponse {
public static void setResponse( WOResponse response, int statusInt, 
String statusString ) {
String contentString = "HTTP/1.0 "+statusInt+" "+statusString;
response.appendContentString( contentString );
response.setHeader( ""+contentString.length(), "content-length" );
response.setHeader( "text/html", "content-type" );
response.setStatus( statusInt );
}
public HTTPStatusResponse( int statusInt, String statusString ) {
super();
HTTPStatusResponse.setResponse( this, statusInt, statusString );
}
}

private static class OKResponse extends HTTPStatusResponse {
public OKResponse() {
super( 200, "OK" );
}
}

This code works for paypal but I try to use it with Google Wallet but it's not 
working.

The answer is
HTTP/1.1 200 Apple
instead of OK !

Can that be the problem and how can I change that ?


Thanks in advance


Pierre
___
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list  (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/webobjects-dev/probert%40macti.ca

This email sent to prob...@macti.ca


___
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list  (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: WOResponse 200 OK

2014-09-19 Thread Pascal Robert
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 WOResponse {
>public static void setResponse( WOResponse response, int statusInt, 
> String statusString ) {
>String contentString = "HTTP/1.0 "+statusInt+" "+statusString;
>response.appendContentString( contentString );
>response.setHeader( ""+contentString.length(), "content-length" );
>response.setHeader( "text/html", "content-type" );
>response.setStatus( statusInt );
>}
>public HTTPStatusResponse( int statusInt, String statusString ) {
>super();
>HTTPStatusResponse.setResponse( this, statusInt, statusString );
>}
>}
> 
>private static class OKResponse extends HTTPStatusResponse {
>public OKResponse() {
>super( 200, "OK" );
>}
>}
> 
> This code works for paypal but I try to use it with Google Wallet but it's 
> not working.
> 
> The answer is
> HTTP/1.1 200 Apple
> instead of OK !
> 
> Can that be the problem and how can I change that ?
> 
> 
> Thanks in advance
> 
> 
> Pierre
> ___
> Do not post admin requests to the list. They will be ignored.
> Webobjects-dev mailing list  (Webobjects-dev@lists.apple.com)
> Help/Unsubscribe/Update your Subscription:
> https://lists.apple.com/mailman/options/webobjects-dev/probert%40macti.ca
> 
> This email sent to prob...@macti.ca

 ___
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list  (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: WOResponse 200 OK

2014-09-19 Thread Dennis Bliefernicht
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 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  (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

WOResponse 200 OK

2014-09-19 Thread Pierre Gilquin

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.0 "+statusInt+" "+statusString;
response.appendContentString( contentString );
response.setHeader( ""+contentString.length(), 
"content-length" );

response.setHeader( "text/html", "content-type" );
response.setStatus( statusInt );
}
public HTTPStatusResponse( int statusInt, String statusString ) {
super();
HTTPStatusResponse.setResponse( this, statusInt, 
statusString );

}
}

private static class OKResponse extends HTTPStatusResponse {
public OKResponse() {
super( 200, "OK" );
}
}

This code works for paypal but I try to use it with Google Wallet but 
it's not working.


The answer is
HTTP/1.1 200 Apple
instead of OK !

Can that be the problem and how can I change that ?


Thanks in advance


Pierre
___
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list  (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com