Get hands-on experience with 20+ free Google Cloud products and $300 in free credit for new customers.

Proxy-Authorization header is not showing in the trace.

Whenever we tried to pass the header Proxy-Authorization it's not being sent and shown in the debug file. But if we use some random header for example test-header in the request we could see it in the trace. Issue only for apigee x. For edge we haven't seen the issue. In the doc I haven't found about the Proxy-Authorization. Is it something predefined one. Why it's not showing in the debug when we passing it on header. We sent a basic get call request  with header Proxy-Authorization. End point mock target. @dchiesa1 @@ganadurai @vidyutverma 

 

majjik98_0-1732044997310.pngmajjik98_1-1732045246315.png

 

majjik98_2-1732045288243.png

 

Solved Solved
0 1 153
1 ACCEPTED SOLUTION

Hi @majjik98 

and thanks for the question. 

The answer is very simple. Proxy-Authorization is a hop-by-hop header. You should not expect to see that header propagated all the way through, by any network proxy, including Apigee.

For more details, see IETF RFC 2616, specifically section 13.5.1 . https://datatracker.ietf.org/doc/html/rfc2616#section-13.5.1


@majjik98 wrote:

For edge we haven't seen the issue.


 

This is a bug in Apigee Edge! It should not be proxying that header.

 

View solution in original post

1 REPLY 1

Hi @majjik98 

and thanks for the question. 

The answer is very simple. Proxy-Authorization is a hop-by-hop header. You should not expect to see that header propagated all the way through, by any network proxy, including Apigee.

For more details, see IETF RFC 2616, specifically section 13.5.1 . https://datatracker.ietf.org/doc/html/rfc2616#section-13.5.1


@majjik98 wrote:

For edge we haven't seen the issue.


 

This is a bug in Apigee Edge! It should not be proxying that header.