[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: HTTPAPI -Header Parser



Hi Athar,

It's unusual for an application to need information from the headers, that's why you haven't seen much discussion in the archives. Normally header data is not needed for anything except httpapi, but in the rare occasion that it is, the application usually just needs a single header, so they just use http_header() to grab that one.

Can you explain why you'd like to iterate through all of them? That seems like a strange thing to do.

Your comment about searching for CRLF,CRLF is a good point. HTTPAPI should definitely NOT be looking at data after the HTTP headers. Though, I don't think it does read past the CRLF,CRLF, because the calling routine only passes the headers to parse_resp_chain, it does not pass the entire response document. The variable names might be a bit misleading, however.

-SK


On 8/5/2016 1:01 PM, Athar Iqbal wrote:
    Hi,


    I am new to this forum, so please forgive me if I ask something that
    has already been asked. I did go through the archives and didn't find
    any information.


    My question is on header parser function in HTTPAPI. Currently,
    header_parse() function reads all the headers and puts them in the data
    structure which is available to the HEADERR4 module only.  In order to
    get the header information, we need to use http_header() function.
    Also, header_parse() goes through the complete response object to pull
    headers from it. Wouldn't it be faster, if it looks for <CRLF><CRLF>
    and stop the search after that?


    I am developing a generic framework to consume web services offered by
    different businesses such MelissaData or D&B. Developers on my team may
    or may not know all the headers coming back in the response object. I
    want to iterate though the all the header and put them in the list and
    return it back to the calling procedure.


    Challenge I am coming across is that there is no iterator that can get
    me all headers without specifying name. Also, could someone please
    explain, what is best use of USERDATA pointer in http_xproc()


    If someone has come across something like this, could you please share.
    If not, I would like to contribute to HTTPAPI by enhancing existing
    code and send it back to the team to see if it is acceptable to include
    in package.


    Again, I apologize in advance, if this has been already discussed and
    if you can point me to some resource.


    Athar


    DISCLAIMER:
    This e-mail is intended for the use of the addressee(s) only and may
    contain privileged, confidential, or proprietary information that is
    exempt from disclosure under law. If you are not the intended
    recipient, please do not read, copy, use or disclose the contents of
    this
    communication to others. Please notify the sender that you have
    received this e-mail in error by replying to the e-mail. Please then
    delete the e-mail and destroy any copies of it. Thank you.



-----------------------------------------------------------------------
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
-----------------------------------------------------------------------