[Xymon] Xymon 4.3.24 Released

[Mark Felder]

> On Nov 24, 2015, at 13:44, J.C. Cleaver <cleaver at terabithia.org> wrote:
> 
> On Tue, November 24, 2015 7:52 am, Mark Felder wrote:
>> On Mon, Nov 23, 2015, at 20:18, J.C. Cleaver wrote:
>>> Hello all,
>>> 
>>> Xymon 4.3.24 has been released and is available on SF.
>>> 
>>> This is a bug fix release that corrects the processing of HTTP Status
>>> codes in xymonnet. Outside of a few specific common HTTP codes, most of
>>> the rest were being flagged incorrectly as Critical errors, instead of
>>> Warnings or OK.
>>> 
>>> The test now works as originally intended.
>>> 
>>> 
>>> All users are encouraged to upgrade.
>>> 
>> 
>> I was just contacted by a user regarding this situation and they noted
>> their 301 redirect was showing up as yellow instead of green. We should
>> really mark 301 as green too...
> 
> 
> Unlike the bug, that being a yellow is actually working as intended. A 301
> being a Permanent Redirect that points to a different URL and indicates to
> the browser to update bookmarks, etc... The reason it wasn't put into the
> same override as 302/303/307 is that it's (in theory) a permanent config
> put in place and not something that would vary based on a transient CMS
> decisions, load balancers, or other dynamic things.
> 
> 
> To duplicate what an end-user is seeing, the "real" URL should be tested
> (since xymonnet isn't following it through); to ensure the previous
> location is perm-redirecting properly (instead of temp redirecting) it
> should be indicated as such with httpstatus=
> 
> 
> That all being said, a way to configure default behavior for each
> installation (a list of overrides checked for before the ranges are used)
> is *definitely* on the list for putting into 4.4. Different administrators
> can clearly have different requirements there.
> 
> 
> Regards,
> -jc
> 


But 301 used to be green, and now users have to change their xymon config to get it to be green again.