Microsoft Content Management Server - trap and notify HTTP 404 error

This is Interesting: Free IT Magazines  
Home > Archive > Microsoft Content Management Server > June 2005 > trap and notify HTTP 404 error





You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

Author trap and notify HTTP 404 error
s.giannone__REMOVETHIS__@giasoft.it

2005-06-28, 5:52 pm

Hi all,

I'd like to know if there is some event that I can handle to manage HTTP
404 error for postings of a MCMS web site.

My goal is to automatically notify to the webmaster (sending an e-mail) that
an URL of a posting that doesn't exist has been requested (maybe 'cause it
was deleted, or it expired... etc.)

I solved this problem mapping ".htm" extension to aspnet_isapi.dll in IIS.
In this way I can handle 404 errors with <customErrors> in web.config file,
etc.

What do you think about this solution?

Thanks,
Bye

Stefano


Stefan [MSFT]

2005-06-28, 5:52 pm

Hi Stefano,

if a 404 happens, then MCMS is not in the picture as MCMS is only involved
if a MCMS manged item is hit.
Any non-MCMS item is handled by IIS.
So if your request is resulting in a 404 then it is not a MCMS manged item
and also not an item IIS knows.
I would recommend to setup a custom 404 error page in IIS rather than
mapping the .htm extension to the ASPNET ISAPI extension.

Cheers,
Stefan

--
This posting is provided "AS IS" with no warranties, and confers no rights

New to MCMS?
Check out this book: Building Websites Using MCMS: http://tinyurl.com/6zj44
----------------------


<s.giannone__REMOVETHIS__@giasoft.it> wrote in message
news:96271e39359c8c74a16e5eded27@msnews.microsoft.com...
> Hi all,
>
> I'd like to know if there is some event that I can handle to manage HTTP
> 404 error for postings of a MCMS web site.
>
> My goal is to automatically notify to the webmaster (sending an e-mail)
> that an URL of a posting that doesn't exist has been requested (maybe
> 'cause it was deleted, or it expired... etc.)
>
> I solved this problem mapping ".htm" extension to aspnet_isapi.dll in IIS.
> In this way I can handle 404 errors with <customErrors> in web.config
> file, etc.
>
> What do you think about this solution?
>
> Thanks,
> Bye
>
> Stefano
>
>



s.giannone__REMOVETHIS__@giasoft.it

2005-06-28, 5:52 pm

> Hi Stefano,

Hi Stefan

> if a 404 happens, then MCMS is not in the picture as MCMS is only
> involved
> if a MCMS manged item is hit.
> Any non-MCMS item is handled by IIS.


It's OK.

[...]

> I would recommend to setup a custom 404 error page in IIS rather than
> mapping the .htm extension to the ASPNET ISAPI extension.


Why?


Stefan [MSFT]

2005-06-28, 5:52 pm

Hi Stefano,

because this would require to have a web.config in the root of the web site
which is not recommended for MCMS as it intercepts with the web.config files
of SiteManager, Authoring connector and your template project.

Cheers,
Stefan

--
This posting is provided "AS IS" with no warranties, and confers no rights

New to MCMS?
Check out this book: Building Websites Using MCMS: http://tinyurl.com/6zj44
----------------------


<s.giannone__REMOVETHIS__@giasoft.it> wrote in message
news:96271e39388c8c74a1ec2014fc9@msnews.microsoft.com...
>
> Hi Stefan
>
>
> It's OK.
>
> [...]
>
>
> Why?
>
>



s.giannone__REMOVETHIS__@giasoft.it

2005-06-29, 2:48 am

> Hi Stefano,

Hi Stefan

> because this would require to have a web.config in the root of the web
> site which is not recommended for MCMS as it intercepts with the
> web.config files of SiteManager, Authoring connector and your template
> project.


My MCMS Asp.net application is already in the root of the web site. I never
had problems with Site Manager, cause I'm using another virtual site for
it. Never used Auth. connector...

This situation is OK for me now.
Anyway, can you suggest me links to documents that describe this problem
(web.config in the root...)?

Thanks,

Bye

Stefano


Stefan [MSFT]

2005-06-29, 7:52 am

Hi Stefano,

sure:
http://download.microsoft.com/downl...6a/MCMS+2002+-+(complete)+FAQ.htm#DD159085-1AFB-4244-AE6D-D0A1C0E9E274

http://download.microsoft.com/downl...6a/MCMS+2002+-+(complete)+FAQ.htm#BE1D9872-BC84-41E7-ABC5-4826E7CF2B85

http://download.microsoft.com/downl...6a/MCMS+2002+-+(complete)+FAQ.htm#53EB2F9B-E87E-442C-8D69-B2B0B783EBB8

Cheers,
Stefan

--
This posting is provided "AS IS" with no warranties, and confers no rights

New to MCMS?
Check out this book: Building Websites Using MCMS: http://tinyurl.com/6zj44
----------------------


<s.giannone__REMOVETHIS__@giasoft.it> wrote in message
news:96271e393c538c74aa1566b91af@msnews.microsoft.com...
>
> Hi Stefan
>
>
> My MCMS Asp.net application is already in the root of the web site. I
> never had problems with Site Manager, cause I'm using another virtual site
> for it. Never used Auth. connector...
>
> This situation is OK for me now.
> Anyway, can you suggest me links to documents that describe this problem
> (web.config in the root...)?
>
> Thanks,
>
> Bye
>
> Stefano
>
>



s.giannone__REMOVETHIS__@giasoft.it

2005-06-29, 7:52 am

> Hi Stefano,

Hi Stefan

> sure:
> http://download.microsoft.com/downl...3a1-4003-9272-2
> 404e92bb76a/MCMS+2002+-+(complete)+FAQ.htm#DD159085-1AFB-4244-AE6D-D0A
> 1C0E9E274
> http://download.microsoft.com/downl...3a1-4003-9272-2
> 404e92bb76a/MCMS+2002+-+(complete)+FAQ.htm#BE1D9872-BC84-41E7-ABC5-482
> 6E7CF2B85
>
> http://download.microsoft.com/downl...3a1-4003-9272-2
> 404e92bb76a/MCMS+2002+-+(complete)+FAQ.htm#53EB2F9B-E87E-442C-8D69-B2B
> 0B783EBB8


OK, Stefan... I already knew that.
Thank you so much!

Bye


Sponsored Links






Free braindumps | Software forum | Database administration forum

Copyright 2003 - 2008 webservertalk.com