That didn't seem to work either, also not with Server.Execute().
long story: I would normally do a redirect, except I am trying to work
around a cross-browser problem. I'm trying to save more state information
than will fit in one cookie. IE handles multiple cookies created in ASP.NET
just fine, but FireFox is not getting all the cookies. (I am guessing that
other "netscape" browsers have the same problem.) ...anyway, should be able
to save session state with a redirect too, but having some sort of problem.
short story: it worked before the SP upgrade!
Any light you can shed on cookie problems with "netscape", specifically
FireFox, would be helpful. I haven't been able to find anything yet.
"Sahil Malik" <co*****************@nospam.com> wrote in message
news:OB**************@TK2MSFTNGP12.phx.gbl...
Try doing ~/Browse.aspx
Incidentally, try and avoid using Server.Transfer. It's legacy carry over
from Classic ASP. Use Server.Execute or even better Response.Redirect.
- Sahil Malik
You can reach me thru my blog
http://www.dotnetjunkies.com/weblog/sahilmalik
"Jack Fox" <ja*****@ix.netcom.com> wrote in message
news:09****************@newsread3.news.pas.earthli nk.net...I just upgraded my XP development machine to SP2, upgraded dotnet
framework 1.1 to sp1, and applied every other outstanding security patch,
and suddenly Server.Transfer in my asp.net website no longer works. I get:
Invalid path for child request
'Browse.aspx?&p=4&q=14569:10.1.0.4;14581:3:6.0:7.3 '. A virtual path is
expected.
What does it mean "virtual path is expected"? Isn't that what I'm giving
it? And it worked yesterday! I didn't change a thing in my project or
IIS.