Not receiving organisation header when a request is routed through Apigee

[srivatsavthumat]

We have a configuration setup to filter apigee routed requests through "X-Apigee.organization" header. However from 25th july some requests intermittently not passing the request header mentioned causing some requests to fail.

I see there is a new release in 25th July is it the reason?

• How do we send custom request headers when routing through Apigee.
• I tried setting up a header and i do not see it in my request. How do i validate it?

[dchiesa1]

The X-Apigee.* headers are not documented, and not supported. It is an error that they appeared at all to your API Proxies. We have now corrected that error.

If you are depending on the presence of those headers, I think you need to modify your API Proxy to not do so.

There is a context variable that provides the organization name. If you want to know the organization name within yoru API Proxy, I suggest you read that variable.

https://docs.apigee.com/api-platform/reference/variables-reference#organization

---

How do we send custom request headers when routing through Apigee.

Just use an AssignMessage policy and set a header.

<AssignMessage name='AM-1'>
  <Set>
    <Headers>
      <Header name='MyHeaderName'>{message-template-here}</Header>
    </Headers>
  </Set>
</AssignMessage>