|
-
Jul 15th, 2008, 06:10 PM
#1
Thread Starter
Fanatic Member
[2005] web.config files error handler
I am using godaddy to host my websites. I have a small problem with using web.config as files error handler. Namely even if i have added custom errors i am still redirected to the godaddy's default 404 page (i am particularly interested in this error).
<customErrors mode="On">
<error statusCode="404" redirect="redirect.aspx" />
</customErrors>
I tried everything and i spent couple hours researching on internet but i came with almost nothing.
I am able to set the 404 error page thorugh their CP but as i have couple domains hosted with the same account it is not acceptable.
What i am doing wrong here?
Thanks
P.S. Maybe it will helps if i mention that this godaddy account works under IIS7
-
Jul 15th, 2008, 06:24 PM
#2
Re: [2005] web.config files error handler
May be This is what you are looking for
__________________
Rate the posts that helped you 
-
Jul 16th, 2008, 03:10 AM
#3
Thread Starter
Fanatic Member
Re: [2005] web.config files error handler
unfortunately the link you left there is not working. At least for me it doesn't work. Could you explain in shorten what i suppose to do in order to work out the web.config error handlers?
Thanks
-
Jul 16th, 2008, 04:31 AM
#4
Thread Starter
Fanatic Member
Re: [2005] web.config files error handler
Is there my favorite helper mendhak maybe? Please my friend i need to fix this asap otherwise i will give up on that. I am pretty sure you know how to handle this issue. You always know 
Thanks
-
Jul 16th, 2008, 03:29 PM
#5
Re: [2005] web.config files error handler
I don't believe that GoDaddy allows you to specify a custom error page in the web.config. That is why they provide you with a way through the control panel.
-
Jul 16th, 2008, 03:29 PM
#6
Re: [2005] web.config files error handler
I say this because my experience of questions on these forums have often shown that godaddy restricts just about everything restrictable. It's best if you contact their support team for confirmation.
-
Jul 16th, 2008, 04:22 PM
#7
Thread Starter
Fanatic Member
Re: [2005] web.config files error handler
I agree about godaddy but i must find solution or change the hosting company as i have multiply domains to ONE account. As per the contacting godaddy; Well i have asked them 24+ hours ago and i am still waiting an answer. lol
Ok i will try to explain the problem simplest possible so maybe we can still find some solution.
It is pretty same idea like those tinyurl (tinyulr.com) website implements. Just please notice that i am not trying to make a clone of it or something. It is so overused and actually there is so many free tinyurl solutions that it's nonsense that i make one more service of that kind.
Rather i want to make that althrough i have multiply domains hosted on a single account that each of them has own 404 error page. That's why i cannot use their generic error page or my single error page .. it is odd that i redirect you to domainB/error404.aspx if you are visiting domainA or domainC
Actually i found this URL Rewritting article and it seems very str8 solution for IIS7 but i have an account which is running under IIS 6.0 and i found that actually Extension-less URL Rewriting for IIS5 and IIS6 is not so easy.
What is nice about this sample and technique is that no server configuration changes are required in order to deploy an ASP.NET application using this approach. It will also work fine in a medium trust shared hosting environment (just ftp/xcopy to the remote server and you are good to go - no installation required).
In addition, i was wondering if i need so complicated solution at all. Actually i figured out that when you type www.domain.com/123 it refers to directory 123 even i expect that it refers a file. So maybe this will give you an idea how can i sort this problem out and make it that when you enter domain.com/123 you are always redirected to domain.com/error404.aspx (if the file/page exists it just proceed normally)
Thanks in advance Master MENDHAK
Last edited by selanec; Jul 16th, 2008 at 04:25 PM.
-
Jul 17th, 2008, 03:16 AM
#8
Re: [2005] web.config files error handler
Then you're better off moving to another host. Godaddy just wasn't created to cater to advanced ASP.NET usage. From what I hear, discontasp.net offers more control and flexibility, which would therefore allow you to perform extensionless URL rewriting in different ways.
-
Jul 20th, 2008, 05:26 PM
#9
Thread Starter
Fanatic Member
Re: [2005] web.config files error handler
Imagine the answer i got received today (godaddy support).
Unfortunately we do not support third party code, scripting or applications beyond ensuring proper connection strings are in place for database and hosting connectivity. You will need to perform online searches or contact the vendor of the software to find more information concerning your issue(s).
And they call this support. they support _ _ _ _
I will certainly move to another host. They become even rude.
check the response i got received a day before the last one;
The general support department cannot help with site design or development issues of your website in this regard. If are not familiar with the development of a custom web.config file to complete the setup of this feature for your hosted sites, you may wish to refer to search engine results for an online tutorial in this regard or contact a website design consultant. We do apologize if this may cause any inconvenience.
Can you believe it?
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|