By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
435,639 Members | 2,262 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 435,639 IT Pros & Developers. It's quick & easy.

Session variables and POST method

P: n/a
I am trying to understand Session variables and ran into a question on
how they work with data that is passed.

I have an HTM file that calls an ASP file and sends the name either by
GET or POST.

When I find is that if I send the value by the GET method,
response.write("From QueryString: " &
Request.QueryString("usernamefromform") & "<br><br>")

will get the variable fine, but

Session("userName")=request.Form("userNameFromForm ")
response.write("Session variable = " & Session("userName"))

doesn't work.

If I use the POST method then it is reversed. Response.QueryString
doesn't get anything and the Session code works.

Why is this? I can't seem to find an explanation in my ASP books.

Thanks,

Tom

Jul 19 '05 #1
Share this Question
Share on Google+
15 Replies


P: n/a
When using method=post, request.Form will not have anything in it. To debug
such a thing or see such a thing, use response.write to see what's going on,
as a general practice.

sTest = Request.form("usernamefromform")
Response.WRite "The value of sTest is " & sTest

Ray at work

"Thomas Scheiderich" <tf*@deltanet.com> wrote in message
news:40**************@deltanet.com...
I am trying to understand Session variables and ran into a question on
how they work with data that is passed.

I have an HTM file that calls an ASP file and sends the name either by
GET or POST.

When I find is that if I send the value by the GET method,
response.write("From QueryString: " &
Request.QueryString("usernamefromform") & "<br><br>")

will get the variable fine, but

Session("userName")=request.Form("userNameFromForm ")
response.write("Session variable = " & Session("userName"))

doesn't work.

If I use the POST method then it is reversed. Response.QueryString
doesn't get anything and the Session code works.

Why is this? I can't seem to find an explanation in my ASP books.

Thanks,

Tom

Jul 19 '05 #2

P: n/a
I meant method=get!

Ray at work

"Ray at <%=sLocation%> [MVP]" <myfirstname at lane34 dot com> wrote in
message news:%2****************@TK2MSFTNGP10.phx.gbl...
When using method=post, request.Form will not have anything in it. To debug such a thing or see such a thing, use response.write to see what's going on, as a general practice.

sTest = Request.form("usernamefromform")
Response.WRite "The value of sTest is " & sTest

Ray at work

"Thomas Scheiderich" <tf*@deltanet.com> wrote in message
news:40**************@deltanet.com...
I am trying to understand Session variables and ran into a question on
how they work with data that is passed.

I have an HTM file that calls an ASP file and sends the name either by
GET or POST.

When I find is that if I send the value by the GET method,
response.write("From QueryString: " &
Request.QueryString("usernamefromform") & "<br><br>")

will get the variable fine, but

Session("userName")=request.Form("userNameFromForm ")
response.write("Session variable = " & Session("userName"))

doesn't work.

If I use the POST method then it is reversed. Response.QueryString
doesn't get anything and the Session code works.

Why is this? I can't seem to find an explanation in my ASP books.

Thanks,

Tom


Jul 19 '05 #3

P: n/a
"Thomas Scheiderich" <tf*@deltanet.com> wrote in message
news:40**************@deltanet.com...
I am trying to understand Session variables and ran into a question on
how they work with data that is passed.

I have an HTM file that calls an ASP file and sends the name either by
GET or POST.

When I find is that if I send the value by the GET method,
response.write("From QueryString: " &
Request.QueryString("usernamefromform") & "<br><br>")

will get the variable fine, but

Session("userName")=request.Form("userNameFromForm ")
response.write("Session variable = " & Session("userName"))

doesn't work.

If I use the POST method then it is reversed. Response.QueryString
doesn't get anything and the Session code works.

Why is this? I can't seem to find an explanation in my ASP books.


When using method GET, you can access the form values via the
Request.Querystring collection. When using method POST, you can access the
form values via the Request.Form collection.

Regards,
Peter Foti
Jul 19 '05 #4

P: n/a
Peter Foti wrote:
"Thomas Scheiderich" <tf*@deltanet.com> wrote in message
news:40**************@deltanet.com...
I am trying to understand Session variables and ran into a question on
how they work with data that is passed.

I have an HTM file that calls an ASP file and sends the name either by
GET or POST.

When I find is that if I send the value by the GET method,
response.write("From QueryString: " &
Request.QueryString("usernamefromform") & "<br><br>")

will get the variable fine, but

Session("userName")=request.Form("userNameFromFo rm")
response.write("Session variable = " & Session("userName"))

doesn't work.

If I use the POST method then it is reversed. Response.QueryString
doesn't get anything and the Session code works.

Why is this? I can't seem to find an explanation in my ASP books.

When using method GET, you can access the form values via the
Request.Querystring collection. When using method POST, you can access the
form values via the Request.Form collection.


Why is that?

Aren't they both forms? I would have thought that the Request.Form,
would still be able to get the data.

I know that the difference between GET and POST is that you can see the
data that is passed in the URL line in your browser, but you can't in
the POST method.

Tom.

Regards,
Peter Foti


Jul 19 '05 #5

P: n/a
Thomas Scheiderich wrote:
Peter Foti wrote:
"Thomas Scheiderich" <tf*@deltanet.com> wrote in message
news:40**************@deltanet.com...
I am trying to understand Session variables and ran into a question
on
how they work with data that is passed.

I have an HTM file that calls an ASP file and sends the name either
by
GET or POST.

When I find is that if I send the value by the GET method,
response.write("From QueryString: " &
Request.QueryString("usernamefromform") & "<br><br>")

will get the variable fine, but

Session("userName")=request.Form("userNameFromForm ")
response.write("Session variable = " & Session("userName"))

doesn't work.

If I use the POST method then it is reversed. Response.QueryString
doesn't get anything and the Session code works.

Why is this? I can't seem to find an explanation in my ASP books.


When using method GET, you can access the form values via the
Request.Querystring collection. When using method POST, you can
access the form values via the Request.Form collection.


Why is that?

Aren't they both forms? I would have thought that the Request.Form,
would still be able to get the data.

I know that the difference between GET and POST is that you can see
the
data that is passed in the URL line in your browser, but you can't in
the POST method.

Tom.

Regards,
Peter Foti


I have never had any problem getting both querystring and form variable
values when using post.

<form action="somepage.asp?qstr=somevalue" method=post>

As you can see, when using post, you have to add the querystring values
yourself, but they do get passed along with the form values.

Bob Barrows
--
Microsoft MVP - ASP/ASP.NET
Please reply to the newsgroup. This email account is my spam trap so I
don't check it very often. If you must reply off-line, then remove the
"NO SPAM"
Jul 19 '05 #6

P: n/a
Thomas Scheiderich wrote:
I am trying to understand Session variables and ran into a question on
how they work with data that is passed.

I have an HTM file that calls an ASP file and sends the name either by
GET or POST.

When I find is that if I send the value by the GET method,
response.write("From QueryString: " &
Request.QueryString("usernamefromform") & "<br><br>")

will get the variable fine, but

Session("userName")=request.Form("userNameFromForm ")
response.write("Session variable = " & Session("userName"))

doesn't work.

What does "doesn't work" mean? We're not looking over your shoulder as you
do these tests ... :-)

Have you verified that request.Form("userNameFromForm") contains a value?
(I'm assuming you changed your submit method to POST when you tried this
....)

Bob Barrows
--
Microsoft MVP - ASP/ASP.NET
Please reply to the newsgroup. This email account is my spam trap so I
don't check it very often. If you must reply off-line, then remove the
"NO SPAM"
Jul 19 '05 #7

P: n/a
Bob Barrows wrote:
Thomas Scheiderich wrote:
I am trying to understand Session variables and ran into a question on
how they work with data that is passed.

I have an HTM file that calls an ASP file and sends the name either by
GET or POST.

When I find is that if I send the value by the GET method,
response.write("From QueryString: " &
Request.QueryString("usernamefromform") & "<br><br>")

will get the variable fine, but

Session("userName")=request.Form("userNameFromFo rm")
response.write("Session variable = " & Session("userName"))

doesn't work.

What does "doesn't work" mean? We're not looking over your shoulder as you
do these tests ... :-)

The page that calls this has this code in it:

<Form action="sessionvar.asp" method="POST">
<input type="text" name="userNameFromForm">
<input type="submit" value="Send It">

When it is like this, the "Session" code works (meaning the second line
will show the userName), but the QueryString will not.

If I change it to GET, the the QueryString will display the name and the
Session code will not.

Have you verified that request.Form("userNameFromForm") contains a value?
(I'm assuming you changed your submit method to POST when you tried this
...)

Yes, I do and it does. As I say, it either works in one or the other
depending on method.

Thanks,

Tom.


Bob Barrows


Jul 19 '05 #8

P: n/a

"Thomas Scheiderich" <tf*@deltanet.com> wrote in message
news:40**************@deltanet.com...

When it is like this, the "Session" code works (meaning the second line
will show the userName), but the QueryString will not.


Your problem isn't session related. It has to do with understanding that
METHOD=GET transfers the form data to the server by means of the querystring
: USER REQUEST.QUERYSTRING.

METHOD=POST transfers the form data to the server by means of post data. :
USE REQUEST.FORM
Method Used | Collection Populated
------------|---------------------
METHOD=POST | Request.Form
METHOD=GET | Request.Querystring
Ray at home
Jul 19 '05 #9

P: n/a
Ray at <%=sLocation%> [MVP] wrote:
"Thomas Scheiderich" <tf*@deltanet.com> wrote in message
news:40**************@deltanet.com...
When it is like this, the "Session" code works (meaning the second line
will show the userName), but the QueryString will not.

Your problem isn't session related. It has to do with understanding that
METHOD=GET transfers the form data to the server by means of the querystring
: USER REQUEST.QUERYSTRING.

METHOD=POST transfers the form data to the server by means of post data. :
USE REQUEST.FORM

What is Post Data and why is it different from the querystring?

Tom.



Method Used | Collection Populated
------------|---------------------
METHOD=POST | Request.Form
METHOD=GET | Request.Querystring
Ray at home


Jul 19 '05 #10

P: n/a
I suggest you buy an ASP book. My favorite beginner's book is Beginning
Active Server Pages 3.0 from Wrox.
http://www.amazon.com/exec/obidos/AS...023492-2159024

Post requests append the form data onto the end of the http request. Get
sticks the data in the url request. Here's a little more info.
http://www.cs.tut.fi/~jkorpela/forms/methods.html

--

Ray at home
Microsoft ASP MVP
"Thomas Scheiderich" <tf*@deltanet.com> wrote in message
news:40**************@deltanet.com...
Ray at <%=sLocation%> [MVP] wrote:
"Thomas Scheiderich" <tf*@deltanet.com> wrote in message
news:40**************@deltanet.com...
When it is like this, the "Session" code works (meaning the second line
will show the userName), but the QueryString will not.


Your problem isn't session related. It has to do with understanding that METHOD=GET transfers the form data to the server by means of the querystring : USER REQUEST.QUERYSTRING.

METHOD=POST transfers the form data to the server by means of post data. : USE REQUEST.FORM

What is Post Data and why is it different from the querystring?

Tom.



Method Used | Collection Populated
------------|---------------------
METHOD=POST | Request.Form
METHOD=GET | Request.Querystring
Ray at home

Jul 19 '05 #11

P: n/a
"Thomas Scheiderich" <tf*@deltanet.com> wrote in message
news:40**************@deltanet.com...
Peter Foti wrote:
"Thomas Scheiderich" <tf*@deltanet.com> wrote in message
news:40**************@deltanet.com...
I am trying to understand Session variables and ran into a question on
how they work with data that is passed.

I have an HTM file that calls an ASP file and sends the name either by
GET or POST.

When I find is that if I send the value by the GET method,
response.write("From QueryString: " &
Request.QueryString("usernamefromform") & "<br><br>")

will get the variable fine, but

Session("userName")=request.Form("userNameFromFo rm")
response.write("Session variable = " & Session("userName"))

doesn't work.

If I use the POST method then it is reversed. Response.QueryString
doesn't get anything and the Session code works.

Why is this? I can't seem to find an explanation in my ASP books.


When using method GET, you can access the form values via the
Request.Querystring collection. When using method POST, you can access the form values via the Request.Form collection.


Why is that?

Aren't they both forms? I would have thought that the Request.Form,
would still be able to get the data.

I know that the difference between GET and POST is that you can see the
data that is passed in the URL line in your browser, but you can't in
the POST method.


The method actually specifies which HTTP method is used to send the form to
the processing agent. With the HTTP "get" method, the form data is appended
to the URI specified by the action attribute, and this new URI is sent to
the processing agent. With the HTTP "post" method, the form data is
included in the body of the form and sent to the processing agent. Thus,
with the "get" method, your form data is transferred to the querystring, and
with the "post" method, it remains in the form.

Hope that helps. For more info, you might try looking up HTTP and/or HTML
Forms (www.w3.org is a good starting point).
Regards,
Peter Foti
Jul 19 '05 #12

P: n/a
Peter Foti wrote:
"Thomas Scheiderich" <tf*@deltanet.com> wrote in message
news:40**************@deltanet.com...
Peter Foti wrote:

"Thomas Scheiderich" <tf*@deltanet.com> wrote in message
news:40**************@deltanet.com...
I am trying to understand Session variables and ran into a question on
how they work with data that is passed.

I have an HTM file that calls an ASP file and sends the name either by
GET or POST.

When I find is that if I send the value by the GET method,
response.write("From QueryString: " &
Request.QueryString("usernamefromform") & "<br><br>")

will get the variable fine, but

Session("userName")=request.Form("userNameFrom Form")
response.write("Session variable = " & Session("userName"))

doesn't work.

If I use the POST method then it is reversed. Response.QueryString
doesn't get anything and the Session code works.

Why is this? I can't seem to find an explanation in my ASP books.
When using method GET, you can access the form values via the
Request.Querystring collection. When using method POST, you can access
the
form values via the Request.Form collection.

Why is that?

Aren't they both forms? I would have thought that the Request.Form,
would still be able to get the data.

I know that the difference between GET and POST is that you can see the
data that is passed in the URL line in your browser, but you can't in
the POST method.


The method actually specifies which HTTP method is used to send the form to
the processing agent. With the HTTP "get" method, the form data is appended
to the URI specified by the action attribute, and this new URI is sent to
the processing agent. With the HTTP "post" method, the form data is
included in the body of the form and sent to the processing agent. Thus,
with the "get" method, your form data is transferred to the querystring, and
with the "post" method, it remains in the form.

This is a "just curious" question as I understand now what "post" does,
but everyone says that the "post" method is appended to the form data
and then passed to the processing agent.

In the "get" method, the URL/URI with the query string appended after
the "?" is sent to the processor. What is actually sent to the
processor for "POST"? When you say the body of the form with the form
data, are you talking about an HTML page that just has the form
information (no graphics,tables etc.).
I assume the data somehow gets sent to the client for the browser to
handle. Where does the data get put for the client to handle for things
such as putting into cookies as well as putting on the screen?

Thanks,

Tom.


Hope that helps. For more info, you might try looking up HTTP and/or HTML
Forms (www.w3.org is a good starting point).
Regards,
Peter Foti


Jul 19 '05 #13

P: n/a
"Thomas Scheiderich" <tf*@deltanet.com> wrote in message
news:40**************@deltanet.com...
Peter Foti wrote:
"Thomas Scheiderich" <tf*@deltanet.com> wrote in message
news:40**************@deltanet.com...
Peter Foti wrote:
"Thomas Scheiderich" <tf*@deltanet.com> wrote in message
news:40**************@deltanet.com...
>I am trying to understand Session variables and ran into a question on
>how they work with data that is passed.
>
>I have an HTM file that calls an ASP file and sends the name either by
>GET or POST.
>
>When I find is that if I send the value by the GET method,
> response.write("From QueryString: " &
>Request.QueryString("usernamefromform") & "<br><br>")
>
> will get the variable fine, but
>
>Session("userName")=request.Form("userNameFrom Form")
>response.write("Session variable = " & Session("userName"))
>
>doesn't work.
>
>If I use the POST method then it is reversed. Response.QueryString
>doesn't get anything and the Session code works.
>
>Why is this? I can't seem to find an explanation in my ASP books.
>
>
When using method GET, you can access the form values via the
Request.Querystring collection. When using method POST, you can access
the
form values via the Request.Form collection.
Why is that?

Aren't they both forms? I would have thought that the Request.Form,
would still be able to get the data.

I know that the difference between GET and POST is that you can see the
data that is passed in the URL line in your browser, but you can't in
the POST method.


The method actually specifies which HTTP method is used to send the form to the processing agent. With the HTTP "get" method, the form data is appended to the URI specified by the action attribute, and this new URI is sent to the processing agent. With the HTTP "post" method, the form data is
included in the body of the form and sent to the processing agent. Thus, with the "get" method, your form data is transferred to the querystring, and with the "post" method, it remains in the form.

This is a "just curious" question as I understand now what "post" does,
but everyone says that the "post" method is appended to the form data
and then passed to the processing agent.

In the "get" method, the URL/URI with the query string appended after
the "?" is sent to the processor. What is actually sent to the
processor for "POST"? When you say the body of the form with the form
data, are you talking about an HTML page that just has the form
information (no graphics,tables etc.).


When a form is submitted for processing, some controls have their name
paired with their current value and these pairs are submitted with the form.
Those controls for which name/value pairs are submitted are called
successful controls.

Read this section of the spec for more details regarding how form data is
processed:
http://www.w3.org/TR/html4/interact/...html#h-17.13.3

In addition, you might read the relavent portions of the HTTP spec (section
9.5 for example):
http://www.ietf.org/rfc/rfc2616.txt

I assume the data somehow gets sent to the client for the browser to
handle. Where does the data get put for the client to handle for things
such as putting into cookies as well as putting on the screen?


Why would you assume such a thing??? Form processing occurs on the server,
not on the client or browser. The server can tell the client that there is
a cookie, and that is handled by each browser individually (as far as where
is stores the cookie).

The spec should answer most of your questions.
Regards,
Peter Foti
Jul 19 '05 #14

P: n/a
Here is what POST and GET requests actually send:
***********post****************
POST /test.asp HTTP/1.1
Accept: image/gif, image/x-xbitmap, image/jpeg, image/pjpeg,
application/msword, application/vnd.ms-excel, application/vnd.ms-powerpoint,
application/x-shockwave-flash, */*
Referer: http://localhost/test.html
Accept-Language: en-us
Content-Type: application/x-www-form-urlencoded
Accept-Encoding: gzip, deflate
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0)
Host: localhost
Content-Length: 59
Connection: Keep-Alive
Cache-Control: no-cache
Cookie: ASPSESSIONIDCABBTSDS=HDMDFOODHJFOJHCCKJIIDOIF

field1=field+1+data&field2=field+2+data&field3=fie ld+3+data


***************get*******************************
GET /test.asp?field1=field+1+data&field2=field+2+data&f ield3=field+3+data
HTTP/1.1
Accept: image/gif, image/x-xbitmap, image/jpeg, image/pjpeg,
application/msword, application/vnd.ms-excel, application/vnd.ms-powerpoint,
application/x-shockwave-flash, */*
Referer: http://localhost/test.html
Accept-Language: en-us
Accept-Encoding: gzip, deflate
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0)
Host: localhost
Connection: Keep-Alive
Cookie: ASPSESSIONIDCABBTSDS=HDMDFOODHJFOJHCCKJIIDOIF
--
Mark Schupp
Head of Development
Integrity eLearning
www.ielearning.com
"Thomas Scheiderich" <tf*@deltanet.com> wrote in message
news:40**************@deltanet.com...
Peter Foti wrote:
"Thomas Scheiderich" <tf*@deltanet.com> wrote in message
news:40**************@deltanet.com...
Peter Foti wrote:
"Thomas Scheiderich" <tf*@deltanet.com> wrote in message
news:40**************@deltanet.com...
>I am trying to understand Session variables and ran into a question on
>how they work with data that is passed.
>
>I have an HTM file that calls an ASP file and sends the name either by
>GET or POST.
>
>When I find is that if I send the value by the GET method,
> response.write("From QueryString: " &
>Request.QueryString("usernamefromform") & "<br><br>")
>
> will get the variable fine, but
>
>Session("userName")=request.Form("userNameFrom Form")
>response.write("Session variable = " & Session("userName"))
>
>doesn't work.
>
>If I use the POST method then it is reversed. Response.QueryString
>doesn't get anything and the Session code works.
>
>Why is this? I can't seem to find an explanation in my ASP books.
>
>
When using method GET, you can access the form values via the
Request.Querystring collection. When using method POST, you can access

the
form values via the Request.Form collection.
Why is that?

Aren't they both forms? I would have thought that the Request.Form,
would still be able to get the data.

I know that the difference between GET and POST is that you can see the
data that is passed in the URL line in your browser, but you can't in
the POST method.


The method actually specifies which HTTP method is used to send the form to the processing agent. With the HTTP "get" method, the form data is appended to the URI specified by the action attribute, and this new URI is sent to the processing agent. With the HTTP "post" method, the form data is
included in the body of the form and sent to the processing agent. Thus, with the "get" method, your form data is transferred to the querystring, and with the "post" method, it remains in the form.

This is a "just curious" question as I understand now what "post" does,
but everyone says that the "post" method is appended to the form data
and then passed to the processing agent.

In the "get" method, the URL/URI with the query string appended after
the "?" is sent to the processor. What is actually sent to the
processor for "POST"? When you say the body of the form with the form
data, are you talking about an HTML page that just has the form
information (no graphics,tables etc.).
I assume the data somehow gets sent to the client for the browser to
handle. Where does the data get put for the client to handle for things
such as putting into cookies as well as putting on the screen?

Thanks,

Tom.


Hope that helps. For more info, you might try looking up HTTP and/or HTML Forms (www.w3.org is a good starting point).
Regards,
Peter Foti

Jul 19 '05 #15

P: n/a
Peter Foti wrote:
"Thomas Scheiderich" <tf*@deltanet.com> wrote in message
news:40**************@deltanet.com...
Peter Foti wrote:

"Thomas Scheiderich" <tf*@deltanet.com> wrote in message
news:40**************@deltanet.com...
Peter Foti wrote:

>"Thomas Scheiderich" <tf*@deltanet.com> wrote in message
>news:40**************@deltanet.com...
>
>
>
>>I am trying to understand Session variables and ran into a question on
>>how they work with data that is passed.
>>
>>I have an HTM file that calls an ASP file and sends the name either by
>>GET or POST.
>>
>>When I find is that if I send the value by the GET method,
>>response.write("From QueryString: " &
>>Request.QueryString("usernamefromform") & "<br><br>")
>>
>>will get the variable fine, but
>>
>>Session("userName")=request.Form("userNameFr omForm")
>>response.write("Session variable = " & Session("userName"))
>>
>>doesn't work.
>>
>>If I use the POST method then it is reversed. Response.QueryString
>>doesn't get anything and the Session code works.
>>
>>Why is this? I can't seem to find an explanation in my ASP books.
>>
>>
>>
>When using method GET, you can access the form values via the
>Request.Querystring collection. When using method POST, you can access
>
>
the
>form values via the Request.Form collection.
>
>
>
Why is that?

Aren't they both forms? I would have thought that the Request.Form,
would still be able to get the data.

I know that the difference between GET and POST is that you can see the
data that is passed in the URL line in your browser, but you can't in
the POST method.
The method actually specifies which HTTP method is used to send the form
to
the processing agent. With the HTTP "get" method, the form data is
appended
to the URI specified by the action attribute, and this new URI is sent
to
the processing agent. With the HTTP "post" method, the form data is
included in the body of the form and sent to the processing agent.
Thus,
with the "get" method, your form data is transferred to the querystring,
and
with the "post" method, it remains in the form.

This is a "just curious" question as I understand now what "post" does,
but everyone says that the "post" method is appended to the form data
and then passed to the processing agent.

In the "get" method, the URL/URI with the query string appended after
the "?" is sent to the processor. What is actually sent to the
processor for "POST"? When you say the body of the form with the form
data, are you talking about an HTML page that just has the form
information (no graphics,tables etc.).


When a form is submitted for processing, some controls have their name
paired with their current value and these pairs are submitted with the form.
Those controls for which name/value pairs are submitted are called
successful controls.

Read this section of the spec for more details regarding how form data is
processed:
http://www.w3.org/TR/html4/interact/...html#h-17.13.3

In addition, you might read the relavent portions of the HTTP spec (section
9.5 for example):
http://www.ietf.org/rfc/rfc2616.txt

That was what I was looking for (this and Marks comments).

Thanks,

Tom.


I assume the data somehow gets sent to the client for the browser to
handle. Where does the data get put for the client to handle for things
such as putting into cookies as well as putting on the screen?


Why would you assume such a thing??? Form processing occurs on the server,
not on the client or browser. The server can tell the client that there is
a cookie, and that is handled by each browser individually (as far as where
is stores the cookie).

The spec should answer most of your questions.
Regards,
Peter Foti


Jul 19 '05 #16

This discussion thread is closed

Replies have been disabled for this discussion.