Get_url_new_session ignoring used alias

Question

Hi,
we have a stateful web application not being in our namespace (it dooesn't start with y or z either) and so we defined an external alias using transaction SICF and stored anonymous logon data there.
Unfortunateley that application needs sap-sycmd=nocookie as parameter which forces mangling the session-id into the url.
If the user clicks a logout-button the follwing code gets executed:
DATA: l_url TYPE string.
* need to call get_url_new_session
* since we have to change the url
* because a new session-id has to be mangled
* into the url
l_url = runtime->get_url_new_session(  'index.do' ).
navigation->exit( l_url ).
l_url holds a newly generated session-id which is quite good but it points to the web application itself for which we can not store anonymous logon data without a modification.
Is there a way to have get_url_new_session recognize the url-path and take it into consideration while creating an url?
In short:
web application: /foo/bar (no logon data in SICF, service not editable without modification)
external alias: /xy/foobar (logon data in SICF)
application is called via: <a href="http://www.example.com/xy/foobar/index.do?sap-syscmd=nocookie">http://www.example.com/xy/foobar/index.do?sap-syscmd=nocookie</a>
after using logout button, method navigation->exit tries to navigate to: <a href="http://www.example.com/sap(<i>some stuff</i>)/bc/bsp/foo/bar/index.do">http://www.example.com/sap(<i>some stuff</i>)/bc/bsp/foo/bar/index.do</a>
result: browser presents http authentication popup
question: how to circumvent?
thanks in advance
Matthias

Answer 1

Hi Daniel,
it doesn't matter whether I use sap-syscmd=nookie or not.
get_url_new_session never takes the used alias into consideration althoug it should be very easy to detect since the url should either be an alias or start with /sap/...)/bc/bsp/
If i call the application using the external alias and syscmd=nocookie all form-tags have an action-attribute pointing to the /sap(...)/bc/bsp/foo/bar which of course leads to an authentication popup after having logged off in /xy/foobar.
If I call the application using the external alias but without sap-syscmd=nocookie there is no single form-tag containing an action-attribute but get_url_new_session will return a link to /sap(...)/bc/bsp/foo/bar as well.
(I know I don't need get_url_new_session in this case)
The implementation of IF_BSP_RUNTIME~GET_URL_NEW_SESSION in CL_BSP_RUNTIME tells us:
* REMARK: this method does NOT set the new BSP to stateful, but does only
*         create a URL that is does work as a stateful URL.
*         For "normal" BSP calls there is no difference between
*         GET_URL_STATELESS, .._NEW_SESSION and ..._SAME_SESSION.
*         Then the session id is transported via a cookie, and a new
*         BSP application means a new session. The result-URL will be identical.
*         The difference between these three methods makes only sense when the session
*         id is transported via URL. This is true, if the applicaion is called with the
*         parameter "sap-syscmd=nocookie", or if it is called from the portal.
*         There are 2 different techniques which are used by the portal:
*         1. the portal calls the application with the nocookie-Parameter
*         2. the portal calls the application with an external sessionid
so I consider this to be a bug too.
But maybe someone else comes up with a solution/explanation?