Re: Status Code 204

[Scott Klement <sk@xxxxxxxxxxxxxxxx>]

The current beta version of HTTPAPI allows header parsing for 204 
response codes.  See here:
http://www.scottklement.com/archives/ftpapi/201501/msg00066.html


On 2/15/2015 12:56 PM, paul.roy@xxxxxxx wrote:
>     Hello
>     I have used HTTPAPI to implement a webservice call to an external
>     service provider who has implement a classical 2 step process
>     1st step is to login and receive a session ID
>     2nd step send the request and receive the response...
>     The problem I am facing is that in some circumstances the response to
>     the fisrt call is a status Code 204 (NO Content) and that the data I
>     need (session ID) is stored in the header part...
>     Debugging my problem, I found that the service program was not decoding
>     the Header when the status code is 204...
>     My understanding of the RFC2016 is that the header should be decoded
>     but again I am more an application programmer...
>     The solution would be to simply change the logic of the srvpgm ...
>     I could just do it but I am not 100% sure that it will have no other
>     consequence on other programs...  and I would prefer from far using a
>     standard version...
>     I also have no experience in 'open source development'.. and I do not
>     know how to proceed... just post my suggested changes here ?
>     What do you suggest ?
>     thank you,
>     Paul
>
>
>
> -----------------------------------------------------------------------
> 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
-----------------------------------------------------------------------