We are excited to announce that the IIS.NET Forums are moving to the new Microsoft Q&A experience. Learn more >

Default HTTP Header when using ISAPIRSS

3 replies

Last post Jun 16, 2009 01:15 PM by Greeno85

  • Default HTTP Header when using ISAPI

    Jun 16, 2009 11:54 AM|Greeno85|LINK

    Hi,

    I am trying to enable keep-alives, but i am scuppered by the connection: close header that keeps returning at the beggining of each response header. Is this due to a default header being sent?

    The headers we add also return, but the connection is not being kept-alive.

    Thanks for your help,

    Andy

     

  • Re: Default HTTP Header when using ISAPI

    Jun 16, 2009 12:11 PM|anilr|LINK

    Can you generate the debug information as per this kb and paste it here?

    Anil Ruia
    Software Design Engineer
    IIS Core Server
  • Re: Default HTTP Header when using ISAPI

    Jun 16, 2009 01:06 PM|Greeno85|LINK

    The application i'm using has many application servers. Will i have to run this kb on one of the app servers?

  • Re: Default HTTP Header when using ISAPI

    Jun 16, 2009 01:15 PM|Greeno85|LINK

     Request:

    POST /abp/IsapiLayerSB.Dll HTTP/1.1

    Content-Type: application/octet-stream

    Content-Length: 186

    Connection: Keep-Alive

    Action: GetClientSecProfile

    User-Agent: THIN TRANSPORT

    Host: devawap6

    Pragma: no-cache

    MCCB�

     Response:

    HTTP/1.1 200 OK

    Connection: close

    Date: Tue, 16 Jun 2009 17:08:35 GMT

    Server: Microsoft-IIS/6.0

    X-Powered-By: ASP.NET

    Connection: Keep-Alive

    Content-Length: 52

    Content-Type: application/octet-stream

    MCCB$

    I don't know if this is any help for the time being? I got the http information using Fiddler. The content length is actually correct when i look at the raw output. Also this is only a debug version and we will not be using content-length and chunked encoding together.

    Thanks,

    Andy