This looks like a fantastic package, though I have been seeing something strange on my first run of it...
Most of the pages are being returned with a purple status of "500 Internal Server Error", but I can visit the page directly just fine and see no visible error.
Do you have any ideas of what I should look at to resolve this incorrect response?
That sounds strange! By default the URL Checker makes a "HEAD" request rather than a "GET" request (which would happen if you used a normal browser). The "HEAD" request just asks the server to return the header info, and not the entire page, when checking if a page exists - which is much faster. It could be something to do with that (if the server can't cope with the request it may throw a wobbly!). You can tweak this by editing DiploLinkChecker.config (in /config/ folder) and change it to "GET".
Is the site you are checking publicly accessible? If so, could you send the URL of one of the pages that returns a 500 server error?
500 Internal Server Error Reported?
This looks like a fantastic package, though I have been seeing something strange on my first run of it...
Most of the pages are being returned with a purple status of "500 Internal Server Error", but I can visit the page directly just fine and see no visible error.
Do you have any ideas of what I should look at to resolve this incorrect response?
The site is umbraco v 4.7.2.
Thanks!
Heather
Hi Heather,
That sounds strange! By default the URL Checker makes a "HEAD" request rather than a "GET" request (which would happen if you used a normal browser). The "HEAD" request just asks the server to return the header info, and not the entire page, when checking if a page exists - which is much faster. It could be something to do with that (if the server can't cope with the request it may throw a wobbly!). You can tweak this by editing DiploLinkChecker.config (in /config/ folder) and change it to "GET".
Is the site you are checking publicly accessible? If so, could you send the URL of one of the pages that returns a 500 server error?
Thanks for the reply, Dan.
I changed it to GET and POST, but with the same result. It is an inherited site, so perhaps something strange is happening in the codebase.
This is the URL: http://www.durexusa.com
~Heather
is working on a reply...
This forum is in read-only mode while we transition to the new forum.
You can continue this topic on the new forum by tapping the "Continue discussion" link below.