IIS Proxy problems with WebAS640SP15

[Former Member]

Hi,

We are using IIS Proxy 1.6 for accessing a custom J2EE application deployed on J2EE engine and for accessing the portal.

We have got a custom loginmodule code which determines access to the applications mentioned above.

This loginmodule redirects to an error web page hosted on IIS under some erroneous condition. Earlier we were using SP9 and the loginmodule code was able to redirect to the error page.

After moving to SP15 we find that under erroneous condition the redirction does not oocur and the browser simply hangs. We dont see any logs updation in the IIS proxy logs during the hanged state.

Has anybody faced similar problems while working with IIS 5 proxy and SP15?

[Benny · Accepted solution]

Hi Alok,

how about checking the code you wrote? It's most unlikely that somebody else can determin this as long we don't know what it does in detail. However, as I know there were changes in that section, it is possible they affect you. But I need more details...

Regards,

Benny

[Former Member · Accepted solution]

Hello Benny,

We perform a redirect in our code as follows:

HttpSetterCallback hscHeaderMsg = new HttpSetterCallback();

HttpSetterCallback hscStatus = new HttpSetterCallback();

Callback[] setterCallbacks = new Callback[2];

setterCallbacks[0] = hscStatus;

setterCallbacks[1] = hscHeaderMsg;

hscHeaderMsg.setType(HttpCallback.SET_HEADER);

hscHeaderMsg.setName("Location");

hscHeaderMsg.setValue(http://mymachine.mydomain.com/ourError.html + "\r\n");

hscStatus.setType(HttpCallback.RESPONSE_CODE);

hscStatus.setName("Response Code");

hscStatus.setValue("302");

}

When we were using SP9 the redirection was happening properly. But after we moved to SP15 the browser hangs at this point and does not redirect to the "ourError.html" page.

Thanks

Alok

[Former Member · Accepted solution]

Alok,

I hope you know that support of IIS Proxy.dll (IISProxy) will be discontinued by SAP.

James

[Former Member · Accepted solution]

James,

Yeah I have read in one of the SAP notes that IIS might now be supported as a reverse proxy. We did some more testing on this and met with partial success. May be the problem is not caused by IIS reverse proxy.

In case of our authentication stack failure we do a redirect to some error page.

The thing I would like to point out is we are facing problems with our code only when we try to do a "redirect" from the code.

i.e. the following code gives problems.

HttpSetterCallback hscHeaderMsg = new HttpSetterCallback();

HttpSetterCallback hscStatus = new HttpSetterCallback();

Callback[] setterCallbacks = new Callback[2];

setterCallbacks[0] = hscStatus;

setterCallbacks[1] = hscHeaderMsg;

hscHeaderMsg.setType(HttpCallback.SET_HEADER);

hscHeaderMsg.setName("Location");

hscHeaderMsg.setValue(http://mymachine.mydomain.com/ourError.html

+ "\r\n");

hscStatus.setType(HttpCallback.RESPONSE_CODE);

hscStatus.setName("Response Code");

hscStatus.setValue("302");

}

callbackHandler.handle(setterCallbacks);

This code results in a hanged state from the browser.

Instead, If we dont do a redirect and simply do an "access forbidden" i.e. Response code "403" from the code as follows:

HttpSetterCallback hscHeaderMsg = new HttpSetterCallback();

HttpSetterCallback hscStatus = new HttpSetterCallback();

hscStatus.setType(HttpCallback.RESPONSE_CODE);

hscStatus.setName("Response Code");

hscStatus.setValue("403");

hscHeaderMsg.setType(HttpCallback.BODY);

hscHeaderMsg.setName("Body");

hscHeaderMsg.setValue("Authentication failed. Check log file for details.");

callbackHandler.handle(setterCallbacks);

then things run fine and we are able to see the message

"Authentication failed. Check log file for details." on the browser.

I am not sure why "redirect" is failing in SP15. It was happening in SP9. Please provide any clues on this. Do we need to change the code to take care of it or some configuration on WebAS side we need to do.

Thanks very much

Alok

[Former Member]

Hi all,

I have a strong suspicion, that most of HttpSetterCallback method do not work in SP15. It would be the answer for your problem - module does not write what you expect to HTTP stream. You might try tool like HTTP Watch to see what portal produces in fact.

In SP2 we used WebCallback, directly accessing HTTP response, but in SP15 it did not work after slight API adaptations, I am afraid. We rewrote the whole module, but without success. Simple demo module written for this case has showed, that there is something writh in HttpSetterCallback. We will continue in explorations, as the problem is vital for us.

Regards,

Pavol