[GRLUG] Slightly OT, .. Bad URL redirect

[Grand Rapids Linux Users Group]

By default, check_http won't follow redirects, since that could be a sign
of something broken/hijacked. You need to use --onredirect:

-f, --onredirect=<ok|warning|critical|follow|sticky|stickyport>
    How to handle redirected pages. sticky is like follow but stick to the
    specified IP address. stickyport also ensures port stays the same.

Not sure if Lynx disables 301's by default too.
Cheers,
John Wesorick
On Fri, Jun 4, 2021 at 3:36 PM Grand Rapids Linux Users Group <
grlug at grlug.org> wrote:

> Trying to fix a redirect problem for a friend that does WordPress:
>
>         usam.com
>
> The browsers I have (FF, Brave, Chromium) resolve OK, but there is
> something wonky with the 301 - lynx cannot resolve, but elinks can??
>
> Most importantly, the Nagios check_http is now failing, but ONLY fails for
> that site.
>
> Tried a half dozen redirect checkers, .. 50% work properly, 50% fail.
>
> Appreciate any insights.
>
>         Thanks!
> --
> grlug mailing list
> grlug at grlug.org
> https://shinobu.grlug.org/mailman/listinfo/grlug
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://shinobu.grlug.org/pipermail/grlug/attachments/20210604/aeb8773b/attachment.html>