Re: url question
From: Kumar Reddi (KumarReddi_at_REMOVETHIS.gmail.com)
Date: 11/30/04
- Next message: Scott Allen: "Re: Application Domain and Hot Deployment"
- Previous message: Kikoz: "Re: url question"
- In reply to: Nikhil Patel: "url question"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 30 Nov 2004 09:38:35 -0500
Your first question about mangled url is, its the session id that you are
seeing in the url. In your web.config, check the sessionState element, in it
check to see that "cookieless" attribure is set to true. If you do not have
a sessionState element in the web.config, then go open your machine.config
file and check the sessionState element in it.
And your second question., its tough to answer, because its a generic
message asp.net throws when you have the customErrors set to RemoteOnly
either in the web.config or machine.config. So, you need to debug on the
remote server where this error is occuring, or turnoff the remoteOnly
feature to see it from anywhere
Good Luck
-- Kumar Reddi http://kumarreddi.blogspot.com "Nikhil Patel" <donotspam@nospaml.com> wrote in message news:uScjKbu1EHA.1400@TK2MSFTNGP11.phx.gbl... > Hi all, > I have installed an ASP.Net application on a production server. When I > type the url for the application, it insterts some strange random string in > the URL. > For example: > If I type http://localhost/opportunitymanager/proposals.aspx in the > address box of the internet explorer, it changes to > http://localhost/opportunitymanager/(k521unec4nw2sd451ex5spje)/proposals.aspx > when the page loads. > > Can you please tell me what causes this? I am asking this because the > application works on the web server. But when I try it on the client > machines, it gives the following error: > > Description: An application error occurred on the server. The current > custom error settings for this application prevent the details of the > application error from being viewed remotely (for security reasons). It > could, however, be viewed by browsers running on the local server machine. > > Details: To enable the details of this specific error message to be viewable > on remote machines, please create a <customErrors> tag within a "web.config" > configuration file located in the root directory of the current web > application. This <customErrors> tag should then have its "mode" attribute > set to "Off". > > <!-- Web.Config Configuration File --> > > <configuration> > <system.web> > <customErrors mode="Off"/> > </system.web> > </configuration> > > Notes: The current error page you are seeing can be replaced by a custom > error page by modifying the "defaultRedirect" attribute of the application's > <customErrors> configuration tag to point to a custom error page URL. > > <!-- Web.Config Configuration File --> > > <configuration> > <system.web> > <customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/> > </system.web> > </configuration> > >
- Next message: Scott Allen: "Re: Application Domain and Hot Deployment"
- Previous message: Kikoz: "Re: url question"
- In reply to: Nikhil Patel: "url question"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
