on 09-04-2003 4:37 PM
Calling a BSP-Page (e.g. /test/test.htm) WebAS redirects to the same page using another URL (e.g. /test(BD1e==)/test.htm).
I think SAP calls this aditional URL code "mangling URL code" and uses it to store sap-theme parameters etc.
We do not need sap-theme parameters. Is there any way to deactivate these mangling code? Or what does WebAS do with this code? Doesn´t it store all user data in a cookie to handle a (stateless) session?
Thank you for your help.
Stefan
Stefan,
It is not possible to decode the URL mangling. It is so deeply ingrained in the BSP, and it mangling will be enforced each time.
There is a BSP application decode_url/default.htm that will tell you what is stored inside the URL.
++bcm
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The mangling code contains usually information like the theme, but also the client or the language. However the amount of content is not always the same it's dynamic dependend on the circumstances.
If the browser doesn't allow cookies additional information like the session ID is handled there. Usually it contains only the necessary information, if the request parameters are the same as the default system parameters (default theme, client, language,...) the code shouldn't appear at all in the URL.
There are technical reasons why not all the information is stored in cookies. AFAIK some internal software layers need the client or language parameters but don't access the request header/body (performace?).
BTW: There's never secret security information "hidden" in the mangling code, of course.
Dirk
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
84 | |
10 | |
9 | |
8 | |
6 | |
6 | |
6 | |
5 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.