for the help.
-Original Message-
From: Frank W. Zammetti [mailto:[EMAIL PROTECTED]
Sent: Monday, May 21, 2007 3:29 PM
To: Tomcat Users List
Cc: users@tomcat.apache.org; [EMAIL PROTECTED]
Subject: Re: Session IDs XMLHttpRequests
I can say with 100% certainty
I'll work on that today.
-Original Message-
From: Hassan Schroeder [mailto:[EMAIL PROTECTED]
Sent: Monday, May 21, 2007 5:32 PM
To: Tomcat Users List
Subject: Re: Session IDs XMLHttpRequests
On 5/21/07, Williams, Allen [EMAIL PROTECTED] wrote:
As I said in my earlier post
: Monday, May 21, 2007 3:29 PM
To: Tomcat Users List
Cc: users@tomcat.apache.org; [EMAIL PROTECTED]
Subject: Re: Session IDs XMLHttpRequests
I can say with 100% certainty that a servlet invoked with
XMLHttpRequest
**DOES** have the same access to server-side objects as a non-AJAX
request. I say
W. Zammetti [mailto:[EMAIL PROTECTED]
Sent: Monday, May 21, 2007 11:29 PM
To: Tomcat Users List
Subject: Re: Session IDs XMLHttpRequests
Let's start with this:
http://www.omnytex.com/test.zip
Just unzip into ${Tomcat}/webapps and try it... the first
time you click
the button you
]
Sent: Tuesday, May 22, 2007 9:17 AM
To: Tomcat Users List
Subject: Re: Session IDs XMLHttpRequests
As long as it's encoded on the url as shown in the example below (and
defined in the servlet spec), tomcat will just pick it up
and use it.
No additional APIs required.
--David
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Allen,
Williams, Allen wrote:
Will it work with POST as well as GET? Although I guess I'll soon find
out;-)
It should work equally well with GET and POST. The browser should send
cookies with every type of request (not just GET and POST).
I
To: Tomcat Users List
Subject: Re: Session IDs XMLHttpRequests
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Allen,
Williams, Allen wrote:
Will it work with POST as well as GET? Although I guess
I'll soon find
out;-)
It should work equally well with GET and POST. The browser should
-
From: Christopher Schultz [mailto:[EMAIL PROTECTED]
Sent: Tuesday, May 22, 2007 10:04 AM
To: Tomcat Users List
Subject: Re: Session IDs XMLHttpRequests
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Allen,
Williams, Allen wrote:
Will it work with POST as well as GET
, 2007 10:04 AM
To: Tomcat Users List
Subject: Re: Session IDs XMLHttpRequests
Allen,
Williams, Allen wrote:
Will it work with POST as well as GET? Although I guess
I'll soon find
out;-)
It should work equally well with GET and POST. The browser
should send
cookies with every type
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Allen,
Williams, Allen wrote:
Now, for the question: how is this ancillary information stored?
The cookie contains all this information. When the cookie is transmitted
to the browser, it contains all this information. Check it using an HTTP
sniffer
Christopher Schultz wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Allen,
...
Firebug must just be showing you selected pieces of information. Web
developer is showing you the browser's view of the world, which includes
the extra metadata.
Update your copy of Firebug if it's not
I had posted this question to four different Java fora over four days
and gotten zero replies, when it occurred to me how stupid not to ask
the community that wrote Tomcat. I was just going to post this, which
is a summary that describes what I've found so far:
-- QUOTE --
In the interest of
I'd say if there are differences, it's in the javascript of the client.
Have you used any sort of monitoring tool to find out if XMLHttpRequest
is sending the session cookie? Have you tried encoding the JSESSIONID
in the XMLHttpRequest via javascript?
--David
Williams, Allen wrote:
I had
I'd say if there are differences, it's in the javascript of
the client.
Yeah, the problem is that the guts of the client JS are pretty opaque.
Have you used any sort of monitoring tool to find out if
XMLHttpRequest
is sending the session cookie?
No, but I was going to modify the
I can say with 100% certainty that a servlet invoked with XMLHttpRequest
**DOES** have the same access to server-side objects as a non-AJAX
request. I say this based on two applications in production that do this
all day long, one Struts-based, one not. I also say it based on a number
of other
Frank W. Zammetti wrote:
I can say with 100% certainty that a servlet invoked with XMLHttpRequest
**DOES** have the same access to server-side objects as a non-AJAX
request. I say this based on two applications in production that do this
all day long, one Struts-based, one not. I also say it
List
Cc: users@tomcat.apache.org; [EMAIL PROTECTED]
Subject: Re: Session IDs XMLHttpRequests
I can say with 100% certainty that a servlet invoked with
XMLHttpRequest
**DOES** have the same access to server-side objects as a non-AJAX
request. I say this based on two applications
for the help.
-Original Message-
From: Frank W. Zammetti [mailto:[EMAIL PROTECTED]
Sent: Monday, May 21, 2007 3:29 PM
To: Tomcat Users List
Cc: users@tomcat.apache.org; [EMAIL PROTECTED]
Subject: Re: Session IDs XMLHttpRequests
I can say with 100% certainty that a servlet invoked
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Allen,
Williams, Allen wrote:
2. What is the difference in the servlet invocation between a regular
URL invocation an XMLHttpInvocation?
I'll be there isn't a difference, actually.
I had a problem in the past where something went wrong and I
19 matches
Mail list logo
