AW: SetError() #13 in recvresp()

["Sawatzki, Peter" <Sawatzki@xxxxxxxxxxxx>]

Scott,

" And, in any case, this string is coming from the HTTP server (not
HTTPAPI) so I don't understand why you are quoting the rules to me."

Yes, I'm aware that the text comes from the server and I quoted the RFC because from the source in HTTPAPIR4 and the message that is printed I mistakenly concluded that httpapi thought that this was incorrect data:

     c                   if        %scan(CR:peRespChain) > 1
     c                   callp     SetError(HTTP_RESP: %subst(peRespChain:1:
     c                                 %scan(CR:peRespChain)-1) )
     c                   else
     c                   callp     SetError(HTTP_RESP: peRespChain)
     c                   endif

-----Ursprüngliche Nachricht-----
Von: ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx [mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx] Im Auftrag von Scott Klement
Gesendet: Montag, 2. Juni 2014 02:51
An: HTTPAPI and FTPAPI Projects
Betreff: Re: SetError() #13 in recvresp()

Peter,

This is normal behavior.  HTTPAPI uses the 'SetError' routine to log the 
status code.    It does not mean that anything is wrong, it only means 
that you got an 'OK' response from the HTTP server.

The format looks exactly correct to me (the version, a space, the '200' 
status code, a space, the textual representation ("OK"), and CRLF at the
end)  This is EXACTLY what the passage from RFC2616 you cited says.

And, in any case, this string is coming from the HTTP server (not
HTTPAPI) so I don't understand why you are quoting the rules to me.

-SK

On 6/1/2014 2:53 AM, Sawatzki, Peter wrote:
> I'm wondering why I have " SetError() #13" errors/warnings in my log:
>
> ----------------------------------------------------------
> 2014-05-31-22.33.49.722000 recvresp(): entered
> HTTP/1.1 200 OK
> Content-Type: text/html
> Last-Modified: Fri, 30 May 2014 07:45:28 GMT
> Accept-Ranges: bytes
> ETag: "a895b20db7bcf1:0"
> Server: Microsoft-IIS/7.0
> X-Powered-By: ASP.NET
> served-by: apptst1
> Date: Sat, 31 May 2014 20:33:49 GMT
> Content-Length: 4
>
>
> 2014-05-31-22.33.49.724000 SetError() #13: HTTP/1.1 200 OK
> 2014-05-31-22.33.49.724000 recvresp(): end with 200
> ----------------------------------------------------------
>
> According to RFC2616 the response header is to be terminated with CRLF and may not contain CR or LF. I looked at the hexdump of the response paket and there is only a CRLF at the end of the  status-line:
>
> HTTP/1.1 200 OK..
> 48 54 54 50 2F 31 2E 31 20 32 30 30 20 4F 4B 0D 0A
>
> RFC2616 defines it this way:
> 6.1 Status-Line
>
> The first line of a Response message is the Status-Line, consisting of the protocol version followed by a numeric status code and its associated textual phrase, with each element separated by SP characters. No CR or LF is allowed except in the final CRLF sequence.
>         Status-Line = HTTP-Version SP Status-Code SP Reason-Phrase 
> CRLF
> ----------------------------------------------------------------------
> - 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
-----------------------------------------------------------------------
-----------------------------------------------------------------------
This is the FTPAPI mailing list.  To unsubscribe, please go to:
http://www.scottklement.com/mailman/listinfo/ftpapi
-----------------------------------------------------------------------