Why am I not able to view/delete the target server name with a colon at the end ?

If I create a target server name with a colon at the end, let's say "https:", then I am not able to view or delete it from the environment. Also I keep seeing the following error whenever I use the Edge UI

1119-targetserverwithcolon.png

I also can't delete this target server.

Solved Solved
0 4 613
1 ACCEPTED SOLUTION

akoo
Participant V

Hi @AMAR DEVEGOWDA,

This looks like a parsing issue in our product-- thank you for bringing it to our attention. Our suggestion would be to not use a target server with a colon at the end, as this looks like a protocol. This is causing problems in the UI (question #1 and #2). You are right that the user should not be allowed to create this in the first place (question #3)-- that is also a bug we will address.

Thank you and please let us know if you have any other questions.

View solution in original post

4 REPLIES 4

This isn't an answer, but @AMAR DEVEGOWDA , I suggest that you contact Apigee Support and have them help you remove that target server from your environment.

@Dino,

Thanks for your response. I already got the target server "https:" removed via Apigee Support.

However, I would like to know the answers to the following questions:

a) Why am I not able to view the target server "https:" in Apigee Edge UI ?

b) Why do I get the Error "Target server https: does not exist in environment prod", even though it exists ?

c) If I am not supposed to create a target server with the colon at the end, then why am I allowed to create such target server in the first place ?

akoo
Participant V

Hi @AMAR DEVEGOWDA,

This looks like a parsing issue in our product-- thank you for bringing it to our attention. Our suggestion would be to not use a target server with a colon at the end, as this looks like a protocol. This is causing problems in the UI (question #1 and #2). You are right that the user should not be allowed to create this in the first place (question #3)-- that is also a bug we will address.

Thank you and please let us know if you have any other questions.

Dear @Alex Koo,

Thanks for your response and accepting that they are bugs and you will address them in a future release.