Re: [xenu-usergroup] WebXM and Xenu
- On Wed, 12 Jan 2005 19:46:44 -0000, frank visser wrote:
>The difference is what you said, that it combines header codes. Xenu
>comparing WebXM (Watchfire) with Xenu i noticed that, with redirects
>(302) leading to a broken link (404), in the case below:
>status code: 302 (object temporarily moved)
>linked from page(s):
>Xenu reports the redirect correctly as 302, though the broken link
>following on that redirect is missed (but can be spotted by enabling
>WebXM seems to combine these to server header codes into one "404", so
>the WebXM reports reads:
>on this page:
>there's a broken link:
>what's the trick here?
>originally i thought WebXM would "miss" these broken links, but since
>it seems to combine 302 + 404 = 404 it does catch these issues.
prefers not to "combine" things.