[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: Exanple18 and HTTP/1.1 500 Internal Server Error
I tried the request to webservicex by using a soap-tester
[1] Vordel SoapBox
[2] WSUnitTest.jar (can't remember from where I got it)
by pasting the SOAP from ex18 into the request
<?xml version="1.0" encoding="iso-8859-1" standalone="no"?><
SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap
/envelope/" xmlns:tns="http://www.webserviceX.NET/";><SOAP
:Body> <tns:ConversionRate> <tns:FromCurrency>USD</tns
:FromCurrency> <tns:ToCurrency>JPY</tns:ToCurrency> </
tns:ConversionRate></SOAP:Body></SOAP:Envelope>
and supply http://www.webservicex.net/CurrencyConvertor.asmx for the URL
http://www.webserviceX.NET/ConversionRate for the soapaction
The [1] didn't allow to send the request because of 'not wellformed
xml....'.
The [2] gave the same result as ex18: HTTP/1.1 500 Internal Server Error.
Then I reconstructed the request:
<?xml version="1.0" encoding="iso-8859-1" standalone="no"?>
<SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/";
xmlns:tns="http://www.webserviceX.NET/";>
<SOAP:Body>
<tns:ConversionRate>
<tns:FromCurrency>USD</tns:FromCurrency>
<tns:ToCurrency>JPY</tns:ToCurrency>
</tns:ConversionRate>
</SOAP:Body>
</SOAP:Envelope>
and... both [1] and [2] where able to send the request and got a valid
response.
Could this point in some direction for the reason why ex18 isn't working ?
Brgds
Helge
-----Original Message-----
From: ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
[mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx]On Behalf Of Scott Klement
Sent: Tuesday, April 01, 2008 9:38 PM
To: HTTPAPI and FTPAPI Projects
Subject: Re: Exanple18 and HTTP/1.1 500 Internal Server Error
I find myself wondering if perhaps your site doesn't have some sort of
transparent proxy that's taking control of the connection. If that
proxy interferes with the HTTP keywords (such as SOAPAction) then I
could see how this could cause a problem with EXAMPLE18-20 but not with
the earlier ones.
But, honestly, that's just a stab in the dark.
Other than the weirdly repeated keywords in the log file (which I don't
get) I don't see anything wrong. I'm afraid you've stumped me, I don't
even know what else to look for.
Helge Bichel wrote:
> Dear Mike.
>
> I had an older LIBHTTP and renamed it to LIBHTTPOLD before restore of
> LIBHTTP 1.22 and run INSTALL with LIBHTTP.
>
> The example18/19/20 didn't work on the old LIBHTTP.
>
> Ping to webservicex.net works fine, and since it get a response (500)
> the connection seems to work.
>
> I haven't realized the problem when running ex18 after ex20 since none
> of then does the job on first instance.
>
> Stange problem.
>
> Best regards
>
> Helge
>
>
>
>
> -----Original Message-----
> From: ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
> [mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx]On Behalf Of Mike Krebs
> Sent: Tuesday, April 01, 2008 5:43 PM
> To: 'HTTPAPI and FTPAPI Projects'
> Subject: RE: Exanple18 and HTTP/1.1 500 Internal Server Error
>
>
> Helge, did you just install HTTPAPI or did you have an older version
> previously? Is there any chance you didn't get a clean install? Have you
> tried running example18 before doing anything else? If I read my debug
file
> correctly, I get a
>
> HTTP/1.1 100 Continue
>
>
> SetError() #13: HTTP/1.1 100 Continue
>
> where you get the 43 error.
>
> If you ping, what does your connection look like (from the System i):
>
> ping 'www.webservicex.net'
> Verifying connection to host system www.webservicex.net at address
> 209.162.186.60.
> PING reply 1 from 209.162.186.60 took 195 ms. 256 bytes. TTL 106.
> PING reply 2 from 209.162.186.60 took 150 ms. 256 bytes. TTL 106.
> PING reply 3 from 209.162.186.60 took 108 ms. 256 bytes. TTL 106.
> PING reply 4 from 209.162.186.60 took 126 ms. 256 bytes. TTL 106.
> PING reply 5 from 209.162.186.60 took 116 ms. 256 bytes. TTL 106.
> Round-trip (in milliseconds) min/avg/max = 108/139/195.
> Connection verification statistics: 5 of 5 successful (100 %).
>
> ***********************************************************
> I ran example18 and it worked just fine.
>
> Example19 runs but tells me:
> The remote server returned an error: (999) Unable to process request at
this
> time -- error 999.
>
> Example20 worked as designed.
>
> When I went back and tried example18 again, I received HTTP/1.1 500
Internal
> Server Error with no debug file. Signoff/on fixed the problem.
>
> For me this is a repeatable problem.
>
> Here are the repeatable steps for the problem I encountered...
> Library LIBHTTP added to library list.
>> call example18 ('USD' 'JPY' 12)
> USD 12.00 = JPY 1221.24
>> call example19 ('French' 'Help me. I need a bathroom')
> The remote server returned an error: (999) Unable to process request at
> this time -- error 999.
>> call example18 ('USD' 'JPY' 12)
> USD 12.00 = JPY 1220.88
>> call example20 ('USD' 'JPY' 12)
> USD 12.00 = JPY 1220.94
>> call example18 ('USD' 'JPY' 12)
> HTTP/1.1 500 Internal Server Error.
>
> Further testing shows calling 18 after 20 never works, but I can call 20
> again and it works (no debug file the second time).
>
> Mike Krebs
>
>
>
> -----Original Message-----
> From: ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
> [mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx] On Behalf Of Helge Bichel
> Sent: Tuesday, April 01, 2008 6:22 AM
> To: HTTPAPI and FTPAPI Projects
> Subject: RE: Exanple18 and HTTP/1.1 500 Internal Server Error
>
> Dear Scott Klement.
>
> Regarding my previous response on this issue:
>
> I have just tried example18 once more and now found the following in
> httpapi_debug.txt:
>
> do_post(): entered
> POST /CurrencyConvertor.asmx HTTP/1.1
> Host: www.webservicex.net
> User-Agent: http-api/1.22
> Content-Type: text/xml
> SOAPAction: http://www.webserviceX.NET/ConversionRate
> Expect: 100-continue
> Content-Length: 347
>
>
> recvresp(): entered
> SetError() #43: CommTCP_read: No 100-Continue (error ignored)
> senddoc(): entered
>
> I see the SOAPActiuon only once, seems to be more correct, but the result
> and other
> error messages about an invalid soapaction are the same.
>
> Brgds
>
> Helge
>
>
>
>
> -----Original Message-----
> From: ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
> [mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx]On Behalf Of Scott Klement
> Sent: Tuesday, April 01, 2008 5:52 AM
> To: HTTPAPI and FTPAPI Projects
> Subject: Re: Exanple18 and HTTP/1.1 500 Internal Server Error
>
>
> Hello Helge,
>
>> returns HTTP/1.1 500 Internal Server Error. Example19 and 20 gives the
>> same result.
> [SNIP]
>> and error '<faultstring>System.Web.Services.Protocols.SoapException:
>> Unable to handle request without a valid action parameter. Please
>> supply a valid soap action. '
>
> This means that there's an error in the "SOAPAction:" keyword that's
> sent to the HTTP server. Here's the relevant part of your log file:
>
>> User-Agent: http-api/1.22
>> Content-Type: text/xml
>>
>> Content-Type:
>> text/xml
>> SOAPAction:
>> [3]http://www.webserviceX.NET/ConversionRate
>> Expect:
>> 100-continue
>> Content-Length:
>> 347
>> SOAPAction:
>> [4]http://www.webserviceX.NET/ConversionRate
>
> I'm a bit confused by this. I'm guessing that the extra linefeeds and
> the [4] were inserted by your e-mail software.
>
> But why are Content-Type and SOAPAction listed twice? Clearly, that
> will cause confusion. You aren't supposed to list these HTTP keywords
> twice. I can't think of any code in HTTPAPI that would do that, and it
> doesn't happen to me when I run EXAMPLE18-20...
>
> So I'm not exactly sure what it could be? Why would those keywords be
> repeated? Also, it looks like there's a blank line after your first
> Content-type.... this would cause major problems as blank lines are
> supposed to indicate the end of the list of headers.
>
> Is anyone else having this problem? I'm not sure what to look for...
-----------------------------------------------------------------------
This is the FTPAPI mailing list. To unsubscribe, please go to:
http://www.scottklement.com/mailman/listinfo/ftpapi
-----------------------------------------------------------------------
-----------------------------------------------------------------------
This is the FTPAPI mailing list. To unsubscribe, please go to:
http://www.scottklement.com/mailman/listinfo/ftpapi
-----------------------------------------------------------------------