I have a scenario where I have to extract # from the uri path for example
apigee.com/proxy/xyz#name=abc
for the above scenario #name=abc not coming even in trace, so is it something that apigee does not support or something else.
I have a scenario where I have to extract # from the uri path
I think you have to reconsider your scenario!
for the above scenario #name=abc not coming even in trace, so is it something that apigee does not support or something else.
Something else.
The # (aka hash, octothorpe) character is handled by the user-agent . According to the HTTP specification, it should never be sent to a server like Apigee. That is probably why you don't see it in Apigee trace.
See also, this previous Q&A.
User | Count |
---|---|
2 | |
1 | |
1 | |
1 | |
1 |