Good Morning,
 
Thanks for the response.  I've been away so just now reading it.  This scenario is on 
a company intranet and the users are supposed to accept cookies.  The odd thing about 
this is that it worked on this person's machine (we're testing right now) and then it 
didn't the next day.  It works on other machines still without a problem.  I can't 
figure out what change would cause this and this person doesn't remember any changes 
happening.  Obviously something changed.  
 
They are using IE 5.0 on an NT desktop.  Anyone know what determines whether IE opens 
new windows in the same process or in a new process.  (That's my thought on what's 
going on.)  
 
Chuck

        -----Original Message----- 
        From: Jayson Falkner [mailto:[EMAIL PROTECTED]] 
        Sent: Sat 8/10/2002 5:09 PM 
        To: [EMAIL PROTECTED] 
        Cc: 
        Subject: Re: New session with windows.open?
        
        

        This issue is more complex than simply using cookies. Web browsers do
        not implement a standard on this - i.e. HTTP doesn't say anything,
        rather, a user configures it. So you can *not* expect a cookie to always
        work fine.
        
        However, you can always expect URL rewriting to work correctly provided
        you are using the correct URL in the window.open() call. Just be sure to
        set the correct URL at runtime in your JavaScript before sending it to a
        client. For example:
        
        window.open("http://www.foo.com";);
        
        would be:
        
        window.open("<%= response.encodeURL("http://www.foo.com";) %>");
        
        And the correct sessionid will be encoded.
        
        Cheers,
        
        Jayson Falkner
        [EMAIL PROTECTED]
        
        Bhangale, Bhushan wrote:
        > Its always happens with every web server when the session is maintained by
        > url reqriting. In case of session by cookie it works fine. So first check by
        > what method the session is being maintained in your server.
        >
        > You can still maintain session in new window by javascript in case of url
        > rewriting by sending the sessionid explicitly in the new window.
        >
        > Hope this helps.........
        >
        > -----Original Message-----
        > From: Charles Kincaid [mailto:[EMAIL PROTECTED]]
        > Sent: Friday, August 09, 2002 4:05 PM
        > To: [EMAIL PROTECTED]
        > Subject: New session with windows.open?
        >
        >
        > Hello,
        >
        > We have an application that is using Tomcat 3.2.4 within IIS on a Windows
        > 2000 Server.
        >
        > The app uses an onclick and "window.open" to open a new window.  Yesterday
        > this worked.  Today it doesn't!
        >
        > We did a quick test with session.GetId() and it has a different session ID
        > for the old and the new windows.  Like I said, though, yesterday (and many
        > days before that) it worked.
        >
        > Anyone know what is going on?  Is this the correct behavior and yesterday
        > was a bug?  What could have changed (as far as I know nothing did, but
        > obviously something did) to cause this change in behavior?
        >
        > Unfortunately, I'm not on-site to be able to play with this directly, but
        > I'll answer any questions I can if I've not given enough info (which is
        > likely).
        >
        > Thanks,
        >
        > Chuck
        >
        >
        > "The information in this e-mail, and any attachment therein, is
        > confidential and for use by the addressee only. If you are not the
        > intended recipient, please return the e-mail to the sender and delete
        > it from your computer. Although The Bank of New York attempts to
        > sweep e-mail and attachments for viruses, it does not guarantee that
        > either are virus-free and accepts no liability for any damage sustained
        > as a result of viruses."
        >
        > ___________________________________________________________________________
        > To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
        > of the message "signoff SERVLET-INTEREST".
        >
        > Archives: http://archives.java.sun.com/archives/servlet-interest.html
        > Resources: http://java.sun.com/products/servlet/external-resources.html
        > LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
        >
        >
        >
        
        ___________________________________________________________________________
        To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
        of the message "signoff SERVLET-INTEREST".
        
        Archives: http://archives.java.sun.com/archives/servlet-interest.html
        Resources: http://java.sun.com/products/servlet/external-resources.html
        LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
        
        

N�����r��zǧu隊[h�+-��ڲ�ܢf�v)ܖ�^�{ay�ʇ�鞲ƠzȠ���HDU,D�51$���b��!����܆+޲6�j˧r��j�!����ǫ�W��{^��-�٥E�(���m���j���w(��k�ۜ���z��z���׫��kz�.�Ǭ�٥,��HDU�i��i��0�[(~�(����楳��z����i


Reply via email to