Domino server losing outbound headers during internal re-direction to the homepage.nsf after a "Get /" request

HCL Domino Domino Forum
1

Hi All,

We are using an application which is acting like a DSAPI filter. Our application has been set to trap the Domino’s kFilterRawRequest, kFilterParsedRequest, kFilterMapURL, kFilterAuthUser and kFilterResponse events. We access the server’s main page from a browser by giving an URL of the form http://dominoserver.mydomain.com:8888. The Home URL setting in the Domino Web server Administration GUI is set to “/homepage.nsf?Open”. Now, when our application receives the “Get /” request, we set a cookie in both the inbound (request) headers and outbound (response) headers. The Domino server had generated the kFilterRawRequest and kFilterParsedRequest events for this “Get /” request.

Now after this, the Domino server internally re-directs to homepage.nsf?Open. For this new request (not sure whether to call this as a new request), the inbound headers set during the previous request are available but the outbound headers are empty. Now we have 2 queries over here:-

  1. If this is a new request, then why are the inbound headers not empty?

  2. If this is the same request, then why are the outbound headers set during the previous request not available for this request?

We also found out that the Domino server did not generate the kFilterResponse event for the initial “Get /” request.

We would like to know that at what stage the inbound headers are committed, since the kFilterResponse event(which commits the headers) was never generated for the “Get /” request.

Any pointers on this would be highly appreciated.

Thanks n Regards,

Atul.

2

Subject: Domino server losing outbound headers during internal re-direction to the homepage.nsf after a “Get /” request.

I am experiencing a similar problem. I notice that noone replied to your very well written post in July.

I have ported an R5 DSAPI filter to R6. I am passing in authentication information on the very first request, then placing these values on a session cookie so that subsequent requests can pick them up and authenticate with the external authentication service.

I then do a redirect back to the client for the initial application page.

My internal redirect to the client comes back with NO cookies in the header.

How come these are getting lost? Or, is there a workaround for this? You would think that most single sign on type of applications would depend somewhat on session cookies.

This code works perfectly in R5.