Special character in URL chopping the URL while API Call

I am exposing a proxy URL in apigee w.r.t. a backend service to check whether special characters present in it or not. Using java script policy validating the special characters present in the URL.

Sending special character "#" in request URL as:

https://hostname:port/employee/3#45?query1=q1&query2=q2

But in the APIGEE end the URL is converting as shown below:

https://hostname:port/employee/3

response.png

Because of that I am not able to validate the special characters present in it.

Can anyone help to provide any solution or suggestion.

Solved Solved
0 4 678
1 ACCEPTED SOLUTION

The # is never sent to a server (like Apigee Edge).

It is known as a Fragment Identifier, and clients don't send that # and what follows it, to the server.

Since Apigee Edge never receives the #, you cannot handle or parse it in Apigee Edge.

side question: why would you ever want to do this?

View solution in original post

4 REPLIES 4

The # is never sent to a server (like Apigee Edge).

It is known as a Fragment Identifier, and clients don't send that # and what follows it, to the server.

Since Apigee Edge never receives the #, you cannot handle or parse it in Apigee Edge.

side question: why would you ever want to do this?

Thanks a lot for the response.

In one scenario we were testing all special characters present in the URL so wanted to know regarding the limitation.

So is there any special character which is allowed and does not get rejected?

Thanks

Can you please ask a new question? And in that new question, please provide some context about what you are trying to do with this special character.

ask-a-new-question.png