Is this a bug?

[Lei Wu]

The following ASP script will display "C:\WINNT\TEMP" on my server:

<%=Request("temp")%>

Is is a bug, or something by design?

The server is a Windows 2000 SP4 running IIS5.

Thanks in advance.

Lei

 

[Bob Barrows]

The following ASP script will display "C:\WINNT\TEMP" on my server:

<%=Request("temp")%>

Is is a bug, or something by design?

The server is a Windows 2000 SP4 running IIS5.

Thanks in advance.

Lei

It is by design. When you don't specify the collection that contains the
variable whose value you want, it searches ALL the collections contained by
the Request object until it finds a variable of that name. That is why you
need to ALWAYS specify the collection you want to use:
<%=Request.querystring("temp")%>
or
<%=Request.Form("temp")%>
or
<%=Request.ServerVariables("temp")%>

HTH,
Bob Barrows

 

[Ray at]

No, it's not a bug. It's returning the server variable TEMP. When you call
Request(something), the server doesn't know if you mean, request.form,
cookies, certificates, etc., so it looks through ALL the collections in this
order:

QueryString
Form
Cookies
ClientCertificate
ServerVariables

Always specify what you mean if you want expected results.

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/iisref/htm/ref_vbom_reqo.asp

Ray at work

 

[Aaron Bertrand - MVP]

The following ASP script will display "C:\WINNT\TEMP" on my server:

<%=Request("temp")%>

Is is a bug, or something by design?

No, this is not a bug.

Using request("") alone is both inefficient and dangerous. First, it will
search /all/ request.* collections until it finds a match. And, if you use
a name that exists in more than one collection, you might get invalid
data...

Use the actual collection you are referring to (e.g. .form, .querystring)
instead of the lazy request("").

In this case, it is actually using Request.ServerVariables.

See http://www.aspfaq.com/2111 for more information.

 

[vivek]

Actually i had the same problem before, but it was doing only one of my
servers and not on the other ones. why would it do it different - its the
exact same code???

Vivek

 

[Aaron Bertrand - MVP]

Actually i had the same problem before, but it was doing only one of my

servers and not on the other ones. why would it do it different - its the
exact same code???

Different versions of IIS, perhaps, process the request collections in a
different order. See
http://msdn.microsoft.com/library/en-us/iisref/htm/ref_vbom_reqo.asp

 

[vivek]

very interesting, thanks Aaron

Vivek

Different versions of IIS, perhaps, process the request collections in a
different order. See
http://msdn.microsoft.com/library/en-us/iisref/htm/ref_vbom_reqo.asp