Request.Form / Request

they worked same but there is a difference when we are using querystring after submitting the forum user can see the details from the header for instance if we user login to this discussion forums through querystring then he can see the password from the header. the only thing is a drawback in querystring but one fine thing is that querystring is fast in process while using form. if you use some softwares to encrypt the header then u may always user querystring.

so just Request.Form or Replace.QueryString is not replace by only Request because the taste of users. If they want request.querystring to use they can and if they want form they can.. So its up to them.... so i think it cant be Request ONly..........

well it depends how big your form is... to if the "get" is best

also, i think its if you have to use the querystring AND the form

then it wont know which to get it from

then why dont you just bloody use it instead of being a prick about it??

the "Request" method is a generic method to get information from either the QuesyString or the Form....

Some people like to be explicit about where the information is coming from and also wish to avoid the possibilty of having both ThisParm in the QueryString AND ThisParam as a posted form field.....

For instance.. version 6 of this forum when you make a new post has a URL like:
http://www.thissite.net/forum/post_message_form.asp?mode=new&ReturnPage=Thread&ForumID=8&TopicID=44933

But on the page generation it also creates a hidden form field called, yup, ForumID
<input type="hidden" name="ForumID" value="8">

Now on postback, if you used just "Request", it'll pull from the URL line first i believe and use that value..... (which is right there for someone to change, say i wanted to "hack" a thread into a protected forum, i could just changed the "8" to the ForumID of the forum i didnt have access to)....  so by explicitly using "Request.Form("ForumID")" the code is pulling from the "hidden" (read: not as easily changable) instead

Morningz,

There is no need to be offensive like that !!!
I could be equally offensive in return, but choose not to do so as it gets us no where.

As a matter of fact, YOU, yes YOU MORNINGZ have missed a few crucial points which I have been advised of since my last post.......

1. Uniqueness
Without specifying what Request needs to search, it will look through not only QueryString and Form, but also Cookies, ClientCertificate and ServerVariables. If there are duplicate names in any of these, then the Request could potentially fail or return the wrong result

2 Performance
With the above in mind, if again you do not specify the 'holder', asp will need to go through each and every object until found.

So, after all, there was a good point to my post. My question was a valid one and I was right to repeat the question 2 or 3 times, although the answer came from elsewhere.

I could have just forgotten about this thread and got on with my work, but no, I thought that the answer was worth sharing with anyone that it may apply to.