Hi Joey,
I don't have experience with Google Checkout integration with Resin, but
maybe I can still help a little bit.
First of all, do you know the content of Authorization-Header from Google?
Something like this:
Authorization: Basic QWxhZGRpbjpvcGVuIHNlc2FtZQ==
The above line contains the BA
Hey Steffen,
Thank you, the authentication appears to be partially working . However I
am still having an issue. I am creating a webservice for Google Checkout,
as shown below. The Basic authentication appears to now be working, as I
can see from the log files, however, when the incoming XML
I think the content-type S text/html; charset=utf-8 is due to the HTML
answer of Resin for 401 Authentication Failed.Usually the sequence of
requests is like this:
1.) Request without authentication header or wrong authentication supplied.
2.) Resin replies with 401 Unauthorized (actually I don't
Hey Steffen,
Thanks once again for your time and help!
I enabled the additional log settings which provide some more data. There
are a couple of questionable items that I thought I may note:
1.) It now shows the content=length: 2882, and the post-data: 2760.
Apparently the entire xml file i
Unfortunately, I am not aware of Hmux when Resin is running behind Apache or
IIS.Are there any further hints about the 401? The Q:quit is logged by the
Hmux Protocol.
I would expect something from com.caucho.server.security.* which indicates a
reason for the 401.
2009/7/14 Mktg. Incorporate Fast
Hi, I've reported to this list, and to mantis, a serious problem I'm
seeing with 4.0.0. I've been hoping for some kind of acknowledgement,
ideally a fix. I seem to have to choose between recompiling JSPs on
every single request, or having Resin reload the entire context when a
single JSP ch
On Jul 14, 2009, at 3:05 PM, Steffen Busch wrote:
Unfortunately, I am not aware of Hmux when Resin is running behind
Apache or IIS.
Are there any further hints about the 401? The Q:quit is logged by
the Hmux Protocol.
I would expect something from com.caucho.server.security.* which
indicat
Hi Scot/Steffen - Both your comments led me to resolve this issue. In
google checkout there is an additional conf file that their API relies on
called checkout-config.xml. This file includes a user/pwd combination that
is must be changed from the default prior to using their API. The comments
by
