Kemp Support, how can we help?

The latest application delivery knowledge and expertise at your fingertips.

Changing from HTTP Status Code 200 to 302 still presents the Error File

 

Information

 

Summary:

This article will discuss a known issue surrounding an existing 200 Status Code on the LoadMaster and caveats as it's transitioned to a Status Code that doesn't present an error file.

Environment:

Product: LoadMaster

Version: 7.2.58 and older.

Platform: Any

Application: Any

Question/Problem Description:

On Virtual Service:
- The 'Not Available Redirection Handling' was set to return a 200 response, returning a static Error File.
- Changing the 'Not Available Redirection Handling' to a 302 response, redirecting to 'https://%h%s' was not honored

Steps to Reproduce:
  1. In the test lab, the Virtual Service was set to a 200 response code/static Error File
  2. The static content is verified and returned as expected
  3. The configuration is changed to 302 / https://%h%s
  4. This was done by first changing the dropdown, then setting the redirect, even if ‘set redirect url’ is clicked after changing the dropdown.
  5. The Virtual Service is still returning the Error File content.
  6. The Virtual Service is changed back to the 200 response code
  7. The radio option is then changed from ‘Error file’ to ‘Error Message’ before changing the dropdown back to 302.
Error Message:  
Defect Number: LM-1867
Enhancement Number:  
Cause: This is a known bug
Resolution:  
Workaround:

Within Advanced Properties, first click the Error Message radio button, then change the Status Code.

StatusCode.png

Notes:  

Comments