Response.Redirect from SSL to non SSL with port drops port.
- From: Sean Wolfe <swolfeAtHubbardOneDotCom_nospam@xxxxxxxxxx>
- Date: Wed, 27 Apr 2005 18:45:43 -0500
I have this wierd bizarrre problem that I'm experienceing with the Response.Redirect() method.
I have a site where the users are on a particular page in SSL. When they post the data back, and the processing is done, it then tries to redirect them back to the non-SSL site. But the site is on a non-starndard port number. I place in the Response.Redirect() method the Fully qualified path to the URL and when ASP.NET makes the Response, the response drops the port number, therefore redirecting the user to a 404.
For example: Users are on a page: https://www.somefqd.com/selectCustomer.aspx?blahblah=blahblah
they post back some data, and then the aspx page process the data, and then a call to Response.Redirect()
Response.Redirect("http://www.somefqd.com:8080/default.aspx");What I end up seeing, using fiddler, the request ends up being http://www.somefd.com/default.aspx.
It's quite strange, becuase I even drop into the debug code and make sure that the string passed to Response.Redirect is the fully qualified path. Any idea's on what is happening here?
Sean .
- Follow-Ups:
- Re: Response.Redirect from SSL to non SSL with port drops port.
- From: Joerg Jooss
- Re: Response.Redirect from SSL to non SSL with port drops port.
- Prev by Date: Re: Global.asax. Need Help. Thank You.
- Next by Date: RE: custom control onblur postback
- Previous by thread: More: Deny direct access to jpg, swf... files, without authentication
- Next by thread: Re: Response.Redirect from SSL to non SSL with port drops port.
- Index(es):
Relevant Pages
|