[ 
https://issues.apache.org/jira/browse/WICKET-4078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13117813#comment-13117813
 ] 

lucius commented on WICKET-4078:
--------------------------------

Hey guys,

Sorry for wasting your time.  But I found out the reason and it might be good 
to share any how.

I have google adsense ads for the site and to use it, I've pasted the google 
supplied javascript.  It will take the 302 redirected url and send a request to 
the server, probably to get some meta data and use it to determine what ads to 
display.  

I looked at that 3rd request to see the origination and it was from google!  So 
if you are using adsense ads you will get a cookie-less request for every click 
causing a new session each click.

Any advise on how to make the call from google stateless or not create a 
session the proper way?

Thanks!
                
> WebApplication.newSession() being called for almost all requests within 1 
> actual session
> ----------------------------------------------------------------------------------------
>
>                 Key: WICKET-4078
>                 URL: https://issues.apache.org/jira/browse/WICKET-4078
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket
>    Affects Versions: 1.5.0, 1.5.1
>         Environment: Wicket 1.5.1 running on jetty 7.5.1 in Ubuntu 
>            Reporter: lucius
>            Priority: Critical
>              Labels: cookie, cookies, jsessionid, redirect, session
>         Attachments: WicketApplication.java
>
>
> IMPORTANT:  This will NOT happen if you are testing it on a local machine or 
> within the LAN.  It only happens if you are connecting through the net, 
> perhaps it requires latency to reproduce.  I'm 100% certain of it as I've 
> been consistently reproducing the same results when I switch b/t LAN and the 
> net.
> Steps to reproduce:
> 1.) create a custom session class
> 2.) in WebApplication override newSession to return your custom session class
> 3.) put a logger in the contructor of the custom session
> 4.) with a browser, navigate around the application from an external machine 
> and see the log that you put in step 3 print out indications of your custom 
> session being created every few clicks.
> This seems to be happening on the redirect where it appends the ?5 after a 
> url?  I'm not sure.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to