Force HTTP Header Configuration
In this document, we will use the information from the actual root cause analysis to make a generic view that can be used if you run into the same or a similar problem in the future. Finally, the document will describe the situation, the problem, the analysis, and the result.
Should you have any questions, please get in touch with academy@emagiz.com.
1. Situation
Header is not accepted by eMagiz.
2. Problem
The standard eMagiz header is not redilvered in the correct format by an external party. eMagiz wants to parse this header, but cannot because it deviates from the standard.
3. Analysis
3.1 Reproduction
After reproduction it was found that the problem reoccured under the same conditions.
3.2 Analysis
When reproducing it was found that additional steps are necessary to prevent the problem from reoccuring.
4. Result
There is a simple workaround to ensure that the problem does not occur anymore. Here we move away from the standard eMagiz behaviour parsing the header that does not comply with the standard. It is done by adding the 'Default HTTP Header Mapper' component and connect it to the 'HTTP outbound gateway' component.