Thomas Joseph wrote:
> When client cookie is disabled, the server should automatically encrypt URLs
> with session data, Right? Is there then any way to fool the server to this
> idea?
>
I'm not sure what you're saying.
A session ID is _added_ to the URL, but it's just that; a session ID.
Not
> I had to solve a similar problem once and I ended up creating an
> This ended up causing a lot of problems.
>
> I dunk (past-tense of "dinked") around with encrypting (using JCE)
>
> I guess that doesn't really answer your question, but maybe it'll spark
> Dave
Thanks
When client cookie is
Thomas Joseph wrote:
> Sorry! The URL needs to be encrypted. The requirement is that the client
> should not be able to see the URLs as plain text on the browser address bar.
>
I had to solve a similar problem once and I ended up creating an
n-character string as a key to look up the "real" URL
From: "Dave Newton" <[EMAIL PROTECTED]>
| Thomas Joseph wrote:
| >> We have a requirement where an existing app needs to have all of its url
references being encoded, even for those that are embedded in hyperlinks.
| > The client wants not to see any of the URLs plainly, as it may contain GET
d
Thomas Joseph wrote:
>> We have a requirement where an existing app needs to have all of its url
>> references being encoded, even for those that are embedded in hyperlinks.
> The client wants not to see any of the URLs plainly, as it may contain GET
> data (ids etc) that is in most cases generat
Hi all,
> We have a requirement where an existing app needs to have all of its url
> references being encoded, even for those that are embedded in hyperlinks.
>
The client wants not to see any of the URLs plainly, as it may contain GET data
(ids etc) that is in most cases generated by embeddin
6 matches
Mail list logo
