DSAPI & Keep-alive connection

HCL Domino Domino Forum
1

Hi

Does anyone knows how DSAPI library in Domino 6 receives new request in keep-alive connection?

i’m trying to support Windows NTLM Authentication in my DSAPI Application.

so in Domino 6 DSAPI is not receiving the new request (not in any event) during the same connection it is just going nowhere!

Opposite to this R5 is handling properly the new request calling “Raw Request” Event and authentication is working fine but only after adding poorly documented instruction “maxrequestperconnection” in httpd.cnf file.

Does anyone have any thoughts about this?

Any info would be appreciated.

Thanks in Advance

2

Subject: DSAPI & Keep-alive connection

Hi Eugene

Did you solve your problem? I am working on the same subject, and have a problem with the Authorization header. It seems like Domino removes this header before the RawRequest event in the third request.

1:

→ GET HTTP/1.1

← 401 Unauthorized | WWW-Authenticate: NTLM

2:

→ GET | Authorization NTLM TlRMT…

← 401 Unauthorized | WWW-Authenticate: NTML TlRMT…

3:

→ GET

According to Page Detailer the request the browser sends contains the Authorization header, put as I wrote, I cannot see it from my filter.

Could it be the “Connection: close” that does it or? Can you write more on your experiences on “maxrequestperconnection”?

3

Subject: DSAPI & Keep-alive connection

Hi again

Having studiet my problem closer, it appears I have the same problem as you Eugene. Have you solved it?

Internet Explorer sends 2 requests on a single connection, and only the first is seen by the filter.

Best regards,

Morten Pedersen

4

Subject: RE: DSAPI & Keep-alive connection

Hi Morten,I have solved this problem in fact,

but to make it worked i had to cheat the standard Domino behavior.

When Domino or your filter sends HTTP Error 401

Domino closes the keep-alive connection at once after that despite any of http headers in your response.

From the IE point of view it looks like some error in transmission channel.

So i had to return HTTP 200 OK & then convert it to HTTP Error 401 on the fly…

Hope this will help to You

Eugene Arsentiev