URLs and case sensitivity is a thorny area, filled with lots of assumed knowledge that is often wrong and implementations that don’t follow standards (only email addresses are worse for this). This is a quick guide to how Apigee deals with the case in a URL.
NB. This is purely for Apigee and is not in any way a full description of URLs e.g. there is nothing about authority (which isn’t allowed by Apigee) or fragments.
A URL is made up of:
| scheme | :// | host | path | query | ||
|---|---|---|---|---|---|---|
| https | :// | api.apigee.enterprise.com | /v1/org/e | ?name=shady | ||
| Case Sensitive? | No | n/a | No (except for shortened names) | Yes (usually) | Yes (usually) |
The errors that are returned vary depending where you put the wrong case. e.g.
https://api.enterprise.apigee.com/V1/o 400 Bad Request
https://api.enterprise.apigee.com/v1/O 404 Not Found
However, if you use the shortened name to call your API, e.g :
http://org-test.apigee.net/tesT302 returns 404
http://org-Test.apigee.net/test302 returns 404