John
The behaviour you are seeing is related to the auto-jump that occurs when a search finds only one matching host. In this situation, it will take you straight to the page with that host in it, rather than an interim page from which to choose from all matching hosts.
My testing shows that the older Xymon returns a "302 Found" redirect, but the new one returns a "200 OK". I'm wondering if this Apache doing some kind of internal redirect for the newer Xymon. The "Location" header sent by the two versions are different in that the old version sends an absolute redirect "Location: http://servername/blabla" and the new one sends a relative redirect "Location: /blabla". I'm not an expert on Apache, but it wouldn't surprise me if it's optimising the relative redirects. If so, this might be a behaviour that can be adjusted by Apache configuration.
J
On 29 March 2018 at 23:36, Rothlisberger, John R. < john.r.rothlisberger at accenture.com> wrote:
Has anyone else noticed that in 4.3.28 the URL is written differently than in previous versions (4.3.21 below)?
It is very useful to know what page a server resides on when using the findhost.sh and being able to send a link that contains the actual path:
https://xymon.server_4.3.21/Chicago/ORD/ORD_TMP/#server1
In 4.3.28 the URL remains with the findhost.sh paramerters:
https://xymon.server_4.3.28/Denver-cgi/findhost.sh?host= server2&jump=on&SUB=Search
Is there a way to revert this back in 4.3.28?
Thanks,
John
Upcoming PTO:
John Rothlisberger
IT Strategy, Infrastructure & Security - Technology Growth Platform
TGP for Business Process Outsourcing
Accenture
312.693.3136 office
This message is for the designated recipient only and may contain privileged, proprietary, or otherwise confidential information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the e-mail by you is prohibited. Where allowed by local law, electronic communications with Accenture and its affiliates, including e-mail and instant messaging (including content), may be scanned by our systems for the purposes of information security and assessment of internal compliance with Accenture policy. Your privacy is important to us. Accenture uses your personal data only in compliance with data protection laws. For further information on how Accenture processes your personal data, please see our privacy statement at https://www.accenture.com/us- en/privacy-policy.
www.accenture.com
Xymon mailing list Xymon at xymon.com http://lists.xymon.com/mailman/listinfo/xymon
To test this hypothesis, I appended XYMONWEBHOST="" to the end of xymonserver.cfg on my Xymon 4.3.10 install, and I was able to reproduce the symptom you described.
The old Xymon uses $XYMONWEBHOST when forming the Location header URL, thus making it an absolute redirect target; whereas the new Xymon leaves $XYMONWEBHOST out, thus making it a relative (to the host) redirect target. Relative targets appear to cause Apache to perform an internal rewrite, transparent to the browser, which only sees the final landing page, yet still with interim "jump" URL.
This change to findhost.cgi may have happened between 4.3.24 and .25, based on this change log entry:
- "Jump to page" redirect functionality fixed on findhost.sh (Reported by Francois Claire)
So it might have been important to fix a fault.
J
On 3 April 2018 at 15:34, Jeremy Laidman <jeremy at laidman.org> wrote:
John
The behaviour you are seeing is related to the auto-jump that occurs when a search finds only one matching host. In this situation, it will take you straight to the page with that host in it, rather than an interim page from which to choose from all matching hosts.
My testing shows that the older Xymon returns a "302 Found" redirect, but the new one returns a "200 OK". I'm wondering if this Apache doing some kind of internal redirect for the newer Xymon. The "Location" header sent by the two versions are different in that the old version sends an absolute redirect "Location: http://servername/blabla" and the new one sends a relative redirect "Location: /blabla". I'm not an expert on Apache, but it wouldn't surprise me if it's optimising the relative redirects. If so, this might be a behaviour that can be adjusted by Apache configuration.
J
On 29 March 2018 at 23:36, Rothlisberger, John R. <john.r.rothlisberger@ accenture.com> wrote:
Has anyone else noticed that in 4.3.28 the URL is written differently than in previous versions (4.3.21 below)?
It is very useful to know what page a server resides on when using the findhost.sh and being able to send a link that contains the actual path:
https://xymon.server_4.3.21/Chicago/ORD/ORD_TMP/#server1
In 4.3.28 the URL remains with the findhost.sh paramerters:
https://xymon.server_4.3.28/Denver-cgi/findhost.sh?host=serv er2&jump=on&SUB=Search
Is there a way to revert this back in 4.3.28?
Thanks,
John
Upcoming PTO:
John Rothlisberger
IT Strategy, Infrastructure & Security - Technology Growth Platform
TGP for Business Process Outsourcing
Accenture
312.693.3136 office
This message is for the designated recipient only and may contain privileged, proprietary, or otherwise confidential information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the e-mail by you is prohibited. Where allowed by local law, electronic communications with Accenture and its affiliates, including e-mail and instant messaging (including content), may be scanned by our systems for the purposes of information security and assessment of internal compliance with Accenture policy. Your privacy is important to us. Accenture uses your personal data only in compliance with data protection laws. For further information on how Accenture processes your personal data, please see our privacy statement at https://www.accenture.com/us-e n/privacy-policy.
www.accenture.com
Xymon mailing list Xymon at xymon.com http://lists.xymon.com/mailman/listinfo/xymon
participants (1)
-
jeremy＠laidman.org