Embedding raw headers in HTTP communications
· 2 min read
New feature added on request by Flowbird integration team:
It is now possible to save raw headers inside the HTTP communication resource.
- This is interesting when the packets are not saved.
- Filtering on headers is not applied on raw headers
- Raw headers are filtered out (like content) when searching HttpCom resources by default, but they can be included with "withContent": true parameter in search body
- Raw headers are automatically included when exporting communications
Effect
The view source link in Headers tab is then working even if packets have not been saved.
Configuration
On the Parsing Config tab of Whisperer settings.
You may also specify URIs for which you want NOT to save rawHeaders (in case of privacy concerns for instance)
Resource change example
In req and res field:
"rawHeaders": {
"content": "GET /v1/posEventStatuses?modulo=1&remainder=0&view=content&afterUpdateMarker%5B%5D=85597012&afterUpdateMarker%5B%5D=38696&range=100 HTTP/1.1\\r\\nAuthorization: JWT eyJhbGci...\\r\\nHost: itproduction\_gateway\\r\\nX-Forwarded-Host: itproduction\_gateway\\r\\nX-Forwarded-For: 10.0.0.129\\r\\nX-Forwarded-BasePath: /terminal/devicemonitoring\\r\\nConnection: close\\r\\nCorrelation-Token: 19IRIKnRm68N0Gl1x6AqtyLtNNa-ztCI",
"size": 2990
}
