date header not passed to backend request
Article ID: 185896
Updated On:
Products
CA API Gateway
API SECURITY
CA API Gateway Precision API Monitoring Module for API Gateway (Layer 7)
CA API Gateway Enterprise Service Manager (Layer 7)
STARTER PACK-7
CA Microgateway
Issue/Introduction
We have problem with date header. We use on one of our API GW as a proxy, but it remove's the date header But when I add it using the add header assertion it's working as expected
Environment
Release : 9.x
Component : API Gateway
Resolution
This is actually expected behavior .
The gateway does not pass a few headers by default . see the following section in the documentation
https://techdocs.broadcom.com/content/broadcom/techdocs/us/en/ca-enterprise-software/layer7-api-management/api-gateway/9-4/policy-assertions/assertion-palette/message-routing-assertions/route-via-http-s-assertion.html
The Gateway does not pass these headers by default, regardless of the pass-through rules defined:
connection
content-encoding
content-length
content-type
datehost
keep-alive
server
transfer-encoding
The Header datehost in this list is supposed to be date and host header !
if you use the add header assertion to set the date header it will be added as a override
The gateway does not pass a few headers by default . see the following section in the documentation
https://techdocs.broadcom.com/content/broadcom/techdocs/us/en/ca-enterprise-software/layer7-api-management/api-gateway/9-4/policy-assertions/assertion-palette/message-routing-assertions/route-via-http-s-assertion.html
The Gateway does not pass these headers by default, regardless of the pass-through rules defined:
connection
content-encoding
content-length
content-type
datehost
keep-alive
server
transfer-encoding
The Header datehost in this list is supposed to be date and host header !
if you use the add header assertion to set the date header it will be added as a override
Feedback
Yes
No
Powered by
