|
Home > Archive > Microsoft Content Management Server > June 2006 > Postings not fully deleted - causing WebAuthorException
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 |
Postings not fully deleted - causing WebAuthorException
|
|
| esccwebteam@googlemail.com 2006-06-14, 1:19 pm |
| We have an archive of press releases on our CMS 2002 SP2 / .NET 1.1
site. Within the press releases channel there's a channel for each
year, and within those a channel for each month.
Recently we decided to delete some of the old press releases. I used
Site Manager on our editing box to select and delete each monthly
channel, and the yearly channels where they were empty. Finally I
emptied the Deleted Items box in Site Manager. I then did the same on
our public box.
Since then we're been catching a lot of WebAuthorExceptions via the
error handling in our global.asax.cs file. The user agent is always
Yahoo Slurp, Googlebot or Ultraseek, and they're always trying to
access one of the deleted postings.
There are no links to these postings now, so I assume these robots have
remembered the URLs from previous visits. If you visit one of the URLs
they're going to in your own browser you just get a 404, as expected,
and no error is thrown. These three bots are obviously getting a
different response when they make the same request, presumably because
their visit places the site under high load.
It seems like some remnant of the postings must remain in order for the
bots to get anything other than a 404. We've tried doing a full export
of that section from our editing box and importing it into our public
box, but it changed nothing. Does anyone have any idea how to stop
these exceptions being thrown?
Details are as follows. Note that the posting in NRORIGINALURL has been
deleted:
Exception Information
----------------------------------------
This operation requires the context of a Posting. The request must
have a valid Posting Url or QueryString so that the
CmsHttpContext.Posting will not be null.
Type: Microsoft.ContentManagement.WebControls.WebAuthorException
Source: Microsoft.ContentManagement.WebControls
Method: Void initializePlaceholderObject() Stack trace:
at
Microsoft.ContentManagement.WebControls.BasePlaceholderControl.initializePlaceholderObject()
at
Microsoft.ContentManagement.WebControls.BasePlaceholderControl.initializeBinding()
at
Microsoft.ContentManagement.WebControls.BasePlaceholderControl.Page_Init(Object
sender, EventArgs e)
at System.EventHandler.Invoke(Object sender, EventArgs e)
at System.Web.UI.Control.OnInit(EventArgs e)
at System.Web.UI.Page.OnInit(EventArgs e)
Help link:
Request.Querystring collection
----------------------------------------
NRMODE: Published
NRORIGINALURL:
/yourcouncil/pressoffice/pressreleases/2003/07/03179mf.htm
NRNODEGUID: {1CAE068C-2587-4961-AF06-6FF1E6EE238C}
NRCACHEHINT: NoModifyGuest
Request.Cookies collection
----------------------------------------
ASP.NET_SessionId: System.Web.HttpCookie
Request.ServerVariables collection (selected values)
----------------------------------------
ALL_RAW: Accept: */*
Accept-Encoding: gzip, x-gzip
If-Modified-Since: Tue, 23 May 2006 19:17:11 GMT
User-Agent: Mozilla/5.0 (compatible; Yahoo! Slurp;
http://help.yahoo.com/help/us/ysearch/slurp)
CONTENT_LENGTH: 0
CONTENT_TYPE:
GATEWAY_INTERFACE: CGI/1.1
HTTPS: off
INSTANCE_ID: 1
PATH_INFO: /yourcouncil/Templates/PressReleases/PressRelease.aspx
QUERY_STRING:
NRMODE=Published& NRORIGINALURL=%2Fyourcouncil%2Fpressoffi
ce%2Fpressreleases%2F2003%2F07%2F03179mf
.htm&NRNODEGUID={1CAE068C-2587-4961-AF06-6FF1E6EE238C}&NRCACHEHINT=NoModifyGuest
REMOTE_ADDR: 68.142.251.93
REMOTE_HOST: 68.142.251.93
REMOTE_PORT: 51199
REQUEST_METHOD: GET
SCRIPT_NAME: /yourcouncil/Templates/PressReleases/PressRelease.aspx
SERVER_PORT: 80
SERVER_PORT_SECURE: 0
SERVER_PROTOCOL: HTTP/1.0
URL: /yourcouncil/Templates/PressReleases/PressRelease.aspx
HTTP_ACCEPT: */*
HTTP_ACCEPT_ENCODING: gzip, x-gzip
HTTP_IF_MODIFIED_SINCE: Tue, 23 May 2006 19:17:11 GMT
HTTP_USER_AGENT: Mozilla/5.0 (compatible; Yahoo! Slurp;
http://help.yahoo.com/help/us/ysearch/slurp)
| |
| Stefan [MSFT] 2006-06-14, 1:19 pm |
| Hi,
you can be sure: after deleting the item and purging the deleted items
folder there is nothing left in the database for the item if the item is a
posting.
For resource gallery items it would be different.
It sounds to me as if the request is coming in using a template URL and not
using posting URL.
E.g. as
/yourcouncil/Templates/PressReleases/PressRelease.aspx?NRMODE=Published& NRORIGINALURL=%2Fyourcouncil%2Fpressoffi
ce%2Fpressreleases%2F2003%2F07%2F03179mf
.htm&NRNODEGUID={1CAE068C-2587-4961-AF06-6FF1E6EE238C}&NRCACHEHINT=NoModifyGuest
This URL will cause the exception you have seen if NRNODEGUID points to a
deleted posting.
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
Check out the new book as well: Advanced MCMS development:
http://tinyurl.com/8ugwj
----------------------
<esccwebteam@googlemail.com> wrote in message
news:1150272788.862029.149320@u72g2000cwu.googlegroups.com...
> We have an archive of press releases on our CMS 2002 SP2 / .NET 1.1
> site. Within the press releases channel there's a channel for each
> year, and within those a channel for each month.
>
> Recently we decided to delete some of the old press releases. I used
> Site Manager on our editing box to select and delete each monthly
> channel, and the yearly channels where they were empty. Finally I
> emptied the Deleted Items box in Site Manager. I then did the same on
> our public box.
>
> Since then we're been catching a lot of WebAuthorExceptions via the
> error handling in our global.asax.cs file. The user agent is always
> Yahoo Slurp, Googlebot or Ultraseek, and they're always trying to
> access one of the deleted postings.
>
> There are no links to these postings now, so I assume these robots have
> remembered the URLs from previous visits. If you visit one of the URLs
> they're going to in your own browser you just get a 404, as expected,
> and no error is thrown. These three bots are obviously getting a
> different response when they make the same request, presumably because
> their visit places the site under high load.
>
> It seems like some remnant of the postings must remain in order for the
> bots to get anything other than a 404. We've tried doing a full export
> of that section from our editing box and importing it into our public
> box, but it changed nothing. Does anyone have any idea how to stop
> these exceptions being thrown?
>
> Details are as follows. Note that the posting in NRORIGINALURL has been
> deleted:
>
> Exception Information
> ----------------------------------------
> This operation requires the context of a Posting. The request must
> have a valid Posting Url or QueryString so that the
> CmsHttpContext.Posting will not be null.
>
> Type: Microsoft.ContentManagement.WebControls.WebAuthorException
> Source: Microsoft.ContentManagement.WebControls
> Method: Void initializePlaceholderObject() Stack trace:
>
> at
> Microsoft.ContentManagement.WebControls.BasePlaceholderControl.initializePlaceholderObject()
> at
> Microsoft.ContentManagement.WebControls.BasePlaceholderControl.initializeBinding()
> at
> Microsoft.ContentManagement.WebControls.BasePlaceholderControl.Page_Init(Object
> sender, EventArgs e)
> at System.EventHandler.Invoke(Object sender, EventArgs e)
> at System.Web.UI.Control.OnInit(EventArgs e)
> at System.Web.UI.Page.OnInit(EventArgs e)
>
> Help link:
>
>
> Request.Querystring collection
> ----------------------------------------
> NRMODE: Published
> NRORIGINALURL:
> /yourcouncil/pressoffice/pressreleases/2003/07/03179mf.htm
> NRNODEGUID: {1CAE068C-2587-4961-AF06-6FF1E6EE238C}
> NRCACHEHINT: NoModifyGuest
>
>
> Request.Cookies collection
> ----------------------------------------
> ASP.NET_SessionId: System.Web.HttpCookie
>
>
> Request.ServerVariables collection (selected values)
> ----------------------------------------
> ALL_RAW: Accept: */*
> Accept-Encoding: gzip, x-gzip
> If-Modified-Since: Tue, 23 May 2006 19:17:11 GMT
> User-Agent: Mozilla/5.0 (compatible; Yahoo! Slurp;
> http://help.yahoo.com/help/us/ysearch/slurp)
>
> CONTENT_LENGTH: 0
> CONTENT_TYPE:
> GATEWAY_INTERFACE: CGI/1.1
> HTTPS: off
> INSTANCE_ID: 1
> PATH_INFO: /yourcouncil/Templates/PressReleases/PressRelease.aspx
> QUERY_STRING:
> NRMODE=Published& NRORIGINALURL=%2Fyourcouncil%2Fpressoffi
ce%2Fpressreleases%2F2003%2F07%2F03179mf
.htm&NRNODEGUID={1CAE068C-2587-4961-AF06-6FF1E6EE238C}&NRCACHEHINT=NoModifyGuest
> REMOTE_ADDR: 68.142.251.93
> REMOTE_HOST: 68.142.251.93
> REMOTE_PORT: 51199
> REQUEST_METHOD: GET
> SCRIPT_NAME: /yourcouncil/Templates/PressReleases/PressRelease.aspx
> SERVER_PORT: 80
> SERVER_PORT_SECURE: 0
> SERVER_PROTOCOL: HTTP/1.0
> URL: /yourcouncil/Templates/PressReleases/PressRelease.aspx
> HTTP_ACCEPT: */*
> HTTP_ACCEPT_ENCODING: gzip, x-gzip
> HTTP_IF_MODIFIED_SINCE: Tue, 23 May 2006 19:17:11 GMT
> HTTP_USER_AGENT: Mozilla/5.0 (compatible; Yahoo! Slurp;
> http://help.yahoo.com/help/us/ysearch/slurp)
>
| |
| esccwebteam@googlemail.com 2006-06-15, 7:20 am |
| Thanks Stefan. I tried requesting postings in that way and got the same
error, so that explains where they're coming from.
The next question is, is there a way to stop them? Can we return a 404
rather than a 500 for those requests so that the robots know not to try
again?
Alternatively, is it ever useful to catch a WebAuthorException or can I
simply set our error handler to ignore them?
| |
| Stefan [MSFT] 2006-06-16, 7:20 am |
| Hi,
not automatically.
What you could do is to implement a error handler that always returns 404
when a 500 server error is raised.
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
Check out the new book as well: Advanced MCMS development:
http://tinyurl.com/8ugwj
----------------------
<esccwebteam@googlemail.com> wrote in message
news:1150360076.549119.198630@h76g2000cwa.googlegroups.com...
> Thanks Stefan. I tried requesting postings in that way and got the same
> error, so that explains where they're coming from.
>
> The next question is, is there a way to stop them? Can we return a 404
> rather than a 500 for those requests so that the robots know not to try
> again?
>
> Alternatively, is it ever useful to catch a WebAuthorException or can I
> simply set our error handler to ignore them?
>
|
|
|
|
|