[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Possible code issue - Re: HTTP/1.1 500 Internal Server Error -
Sender: "Richard ECUYER" <recuyer@xxxxxxx>
Oups ! big mistake sorry.
I will code it :
Select ;
When %parms <5
....
When %parms > 9
Other (5<=parms<=9)
Endsl
so you have 3 choices
----- Original Message -----
From: "Richard ECUYER" <recuyer@xxxxxxx>
To: <ftpapi@xxxxxxxxxxxxx>
Sent: Friday, September 16, 2005 5:05 PM
Subject: Re: Possible code issue - Re: HTTP/1.1 500 Internal Server Error -
> Sender: "Richard ECUYER" <recuyer@xxxxxxx>
>
> it work like it must work :
>
> Only 2 possibilities :
> parms < 7 or parms >= 7 .
> nothing else.
> you must code it :
>
> when parms < 7 ==> if <7
> ..
> when parms < 8 ==> only if = 7
> ...
>
> when parms < 9 ==> only if = 8
> ...
> and so on
>
>
> other only if >= last coded
> ...
>
> ----- Original Message -----
> From: <nellestj@xxxxxxx>
> To: <ftpapi@xxxxxxxxxxxxx>
> Sent: Friday, September 16, 2005 4:22 PM
> Subject: Possible code issue - Re: HTTP/1.1 500 Internal Server Error -
>
>
> > Sender: <nellestj@xxxxxxx>
> >
> > In looking through this code we found that it was actually getting hung
up
> in the HTTPXMLR4 program. We are sending 10 parameters, but because of
how
> the program is coded, it never hits where it should, the OTHER. Can we
> change/recompile just that program? Here's what it has:
> > select;
> > when (%parms < 7);
> > wwRC = http_url_post_raw( peURL
> > : pePostData
> > : pePostDataLen
> > : 5
> > : %paddr(ParseXML) );
> > when (%parms >= 7);
> > wwRC = http_url_post_raw( peURL
> > : pePostData
> > : pePostDataLen
> > : 6
> > : %paddr(ParseXML)
> > : peTimeout );
> > when (%parms >= 8);
> > wwRC = http_url_post_raw( peURL
> > : pePostData
> > : pePostDataLen
> > : 7
> > : %paddr(ParseXML)
> > : peTimeout
> > : peUserAgent );
> > when (%parms >= 9);
> > wwRC = http_url_post_raw( peURL
> > : pePostData
> > : pePostDataLen
> > : 8
> > : %paddr(ParseXML)
> > : peTimeout :
> peContentType );
> > other;
> > wwRC = http_url_post_raw( peURL
> > : pePostData
> > : pePostDataLen
> > : 9
> > : %paddr(ParseXML)
> > : peTimeout
> > : peUserAgent
> > : peContentType
> > : peSOAPAction ) ;
> > endsl;
> > >
> > > From: Scott Klement <sk@xxxxxxxxxxxxxxxx>
> > > Date: 2005/09/15 Thu PM 08:27:21 GMT
> > > To: ftpapi@xxxxxxxxxxxxx
> > > Subject: Re: HTTP/1.1 500 Internal Server Error
> > >
> > > Sender: Scott Klement <sk@xxxxxxxxxxxxxxxx>
> > >
> > > > I am receiving the HTTP/1.1 500 Internal Server Error with the
> > > > http_url_post_xml(). Any suggestions on where to look for an answer?
> > >
> > > HTTPAPI is an HTTP client. It connects to HTTP servers and issues
> > > commands to them.
> > >
> > > When something goes wrong on the server (usually program that it calls
> is
> > > crashing or otherwise ending abnormally) the server will report "500
> > > Internal Server Error"
> > >
> > > So the question becomes, what's going wrong on the server that's
causing
> > > it to crash?
> > >
> > > a) Are you sending something incorrect? A well-written server
> > > shouldn't just crash because you sent it invalid data, instead
> > > it should tell you what you did wrong. However, there are a
lot
> > > of servers out there that aren't well written.
> > >
> > > b) Is there a bug in HTTPAPI that may be causing IT to send
> something
> > > incorrect?
> > >
> > > c) Is everything you're sending correct, but there's just a bug in
> > > the server code?
> > >
> > > It's awfully hard to narrow something like this down when all you know
> is
> > > that some kind of error occurred on the server. It sure would be
easier
> > > if we knew what the error was, instead of just "an error occurred".
> > >
> > > One thing in your code that did make me raise an eyebrow was that
you're
> > > telling the server that your document is encoded with UTF-8. It sure
> > > doesn't look like UTF-8 to me! It looks like EBCDIC data in an RPG
> > > variable. Granted, it won't be EBCDIC when it hits the server, since
> > > HTTPAPI will translate it, but it won't be UTF-8 either. It'll
probably
> > > be ISO-8859-1.
> > >
> > > I don't know if that has anything to do with the error or not.
> > >
> > > If you can't figure it out by trial and error, you'll probably have to
> > > contact the server's admin and see if he can give you more info about
> > > what's going wrong.
> > >
> > > Usually, when an internal server error is sent to the HTTP client, the
> > > server will also make a log with more detail about what went wrong.
The
> > > server's admin should be able to look at that log and provide you with
> > > more more info.
> >
> -----------------------------------------------------------------------
> > > This is the FTPAPI mailing list. To unsubsribe from the list send
mail
> > > to majordomo@xxxxxxxxxxxxx with the body: unsubscribe ftpapi
mymailaddr
> >
> -----------------------------------------------------------------------
> > >
> >
> > -----------------------------------------------------------------------
> > This is the FTPAPI mailing list. To unsubsribe from the list send mail
> > to majordomo@xxxxxxxxxxxxx with the body: unsubscribe ftpapi mymailaddr
> > -----------------------------------------------------------------------
> >
>
> -----------------------------------------------------------------------
> This is the FTPAPI mailing list. To unsubsribe from the list send mail
> to majordomo@xxxxxxxxxxxxx with the body: unsubscribe ftpapi mymailaddr
> -----------------------------------------------------------------------
>
-----------------------------------------------------------------------
This is the FTPAPI mailing list. To unsubsribe from the list send mail
to majordomo@xxxxxxxxxxxxx with the body: unsubscribe ftpapi mymailaddr
-----------------------------------------------------------------------