Highlighted
New Member.
313 views

Console/output log without response body when occurs 503

Hi all,

I'm receiving response status as 503 from a request but checking the output/console log information there isn't response body data (only header), even the "runtime setting" configured with Extended Log and all options checked (Log HTTP resquest/response header and body). 

Checking this same request using postman/cURL, the response body has message data. Is there an option to collect this response body when we have status code different than 200?

Thanks in advance

0 Likes
3 Replies
Highlighted
Acclaimed Contributor.. Acclaimed Contributor..
Acclaimed Contributor..

Re: Console/output log without response body when occurs 503

Just a quick idea:

Did you try to set a large value for web_set_max_html_param_len("10240"); (depending on the expected size) and use e.g.

web_reg_save_param_regexp (
"ParamName=RawBody",
"RegExp=(.*)",
"Scope=Body",    // "Scope=All"
"Notfound=warning",
LAST);

To capture the complete body or message?

Signature:
Reward community members who take time to respond and help.
0 Likes
Highlighted
New Member.

Re: Console/output log without response body when occurs 503

Thanks JHF for the idea!!

We are using the truclient_step and we want to capture all the response content but in special the response body because it has a message that using the default runtime settings configuration, like the "extended log" , it was not stored/logged.

0 Likes
Highlighted
Super Contributor.
Super Contributor.

Re: Console/output log without response body when occurs 503

Just another quick idea - are you sure the server is sending any body at all when replying with HTTP 503?

(How to check? With some luck your web server logs in its Access log file both status code, i.e., 503, and size of response, in bytes. Or maybe you're lucky enough to be able to get the HTTP 503 in some other tool during the high load period - maybe by using a web browser?)

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.