Note that there are some explanatory texts on larger screens.

plurals
  1. PODesign solution for URL encoding
    primarykey
    data
    text
    <p>I am planning a URL rewriter/encoder (maybe rewriter is a better term). The main purpose is to hide the exact URL from the client, since if he is smart enough, he can figure out how to mess up the application. </p> <p>The URL encoder would be an injective function <code>f(x) = y</code>. The decoder would be the inverse function of <strong>f</strong>, say <strong>g</strong> such that <code>g(y) = x</code>. This way I can encode and decode my URLs.</p> <p>A URL like:</p> <p><a href="http://www.myapp.com/servlet/myapp/template/MyScreen.vm/action/MyAction" rel="nofollow noreferrer">http://www.myapp.com/servlet/myapp/template/MyScreen.vm/action/MyAction</a> would be encoded to something like:</p> <p><a href="http://www.myapp.com/uyatsd6787asv6dyuasgbdxuasydgb876876v" rel="nofollow noreferrer">http://www.myapp.com/uyatsd6787asv6dyuasgbdxuasydgb876876v</a></p> <p>It does not matter what is in the encoded URL as far as it is not understandable.</p> <p>The problem is that I do not know how to manipulate the URL that the browser displays. I am using JBoss as a servlet container and Turbine servlet as the web application framework. I would need a module that receives the encoded URL, decodes it, passes it to Turbine, then it modifies the response's URL to show the encoded URL again. </p> <p><strong>Previous attempts to solve the problem:</strong> I have created a servlet filter, but I can not access the URL since the filter receives a ServletRequest that is a JBoss implementation. As far as I have read it seems that a servlet filter is not a good choice for manipulating the URL. </p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload