Space in querystring

braindead

Hi All

Is

1. dopage.asp?<% =SessionID=value_here%> is different tha
2. dopage.asp?<%=SessionID=value_here%> ??

Please note that there is a space between the asp tags and the = sign in the first item. I thought ASP will treat #1 and #2 as the same. However it seems that is not the case. Has anybody seen this before

Please let me know.

Thanks

Jul 19 '05 #1

Ray at

Shouldn't make a difference. Explain what seems to be different or show us
what seems to be different in the results of the two. What is that
querystring supposed to result in anyway? ?sessionid=xxxxxxxxxxxx? Or do
you have a variable named SessionID? Do you want a boolean result?

Ray at work

"braindead" <an*******@discussions.microsoft.com> wrote in message
news:96**********************************@microsof t.com...

Hi All,

Is

1. dopage.asp?<% =SessionID=value_here%> is different than
2. dopage.asp?<%=SessionID=value_here%> ???

Please note that there is a space between the asp tags and the = sign in the first item. I thought ASP will treat #1 and #2 as the same. However it
seems that is not the case. Has anybody seen this before?
Please let me know.

Thanks

Jul 19 '05 #2

braindead

Thanks for the reply

What is that querystring supposed to result in anyway? ?sessionid=xxxxxxxxxxxx?
Or do you have a variable named SessionID? Do you want a boolean resul
We are using a variable SessionID ( GUID) to keep track of the user and this ID is passed between pages, in the querystring. Each page checks for SessionID, and if not valid/or not there, User is forced back to login page( user session timedout)
Explain what seems to be different or show us what seems to be different in the results of the two.

While researching on this session timeout issue, I found that, on the 3 pages, where the timeout occurs ( randomly!), there is a sapce between the <% tag and the = sign. Well, that is the only issue, if any, I could find. I was wondering whether anybody has seen this before

Hope this helps

Thank

Jul 19 '05 #3