I don't agree. There are two ways for a jsessionid to be provided from
a browser to a servelt container. a) url parameter b) http header. I'm
not really an expert on this but as far as I know it is a matter of
servlet container config and the reason there are two options is
because of SSL. The url
I filed a bug that basically states that we should be applying the same
behavior consistently across static Images and ResourceLinks to static
images.
Gili
Juergen Donnerstag wrote:
I don't agree. There are two ways for a jsessionid to be provided from
a browser to a servelt container. a) url
if you send a session id with the url or the header
Then the image can also be stale (not cacheable) Because it is session
bound
So we should try to avoid a session state being attached on a image
link (a static link ofcourse which doesn't change)
johan
Juergen Donnerstag wrote:
I don't
Iiigo,
On 4/23/05, liigo [EMAIL PROTECTED] wrote:
Two things that I can't understand easily, just in the HelloWord
application.
With the HelloWord demo application code following:
package wicket.examples.helloworld;
import wicket.markup.html.WebPage;
import wicket.markup.html.basic.Label;
liigo wrote:
Two things that I can't understand easily, just in the HelloWord
application.
With the HelloWord demo application code following:
package wicket.examples.helloworld;
import wicket.markup.html.WebPage;
import wicket.markup.html.basic.Label;
public class HelloWorld extends WebPage
{
