We help IT Professionals succeed at work.

Check out our new AWS podcast with Certified Expert, Phil Phillips! Listen to "How to Execute a Seamless AWS Migration" on EE or on your favorite podcast platform. Listen Now

x

Custom message instead of standard HTTP error 404 with IIS?

marcelgr090398
on
Medium Priority
251 Views
Last Modified: 2010-04-09
I'm not sure if this question belongs in this group, because it is actualy an IIS question (I think). I hope someone can answer it.
We have a web server (Internet Information Server). If an internet user requests a page that is not on our server, he will get an HTTP error 404. I've seen some other website that return a custom html-file that tells you that this page doesn't exist. That is what I want too, but how do I do it?
Comment
Watch Question

Commented:
Unlock this solution with a free trial preview.
(No credit card required)
Get Preview

Author

Commented:
I'm sorry, I didn't provide very much information.
We have Windows NT Server 4.0 SP2 running IIS 3.0
We don't have Microsoft Management Console, or Option Pack.
We use Internet Service Manager that comes with IIS3.0
I can not find any setting in Internet Service Manager to select a custom file for the 404 error (or any error).

Is it posible with IIS4 to use a custom 404 error page on a per server basis, or also on a per web basis?

Marcel

Commented:
Marcel,

Yes and yes. (you can use a custom message -- WITH IIs4 --  on a per server and per Web basis). Recommend you get SP3 for NT and also the OptionPak which upgrades IIs to version 4. OptionPak is a huge download (40MB+) but solves the error issue; has better logging options, etc. The Management Console (Internet Service Manager for IIs4) is in the OptionPak -- very different from what you've seen with IIs3, but it works.

I THINK IIs3 allowed you to define a single custom error message via the registry, but have purged that from memory at this point.

Only hesitation to doing this upgrade would be if you've done a lot of ASP or ISAPI scripting under 3.0. [CGIs may need some changes -- our biggest headbanger involved header issues dealing with http1.0 (all but IE4+) and http1.1 (IE4) clients].

Good luck!

Raoool

Author

Commented:
thanks a lot.
we will consider upgrading to IIS4
Unlock the solution to this question.
Thanks for using Experts Exchange.

Please provide your email to receive a free trial preview!

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

OR

Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.