![]() ![]() Have you confirmed the timestamp you are passing should include the 'T' character (the date/time separator). If you can publish your readyapi, http and error logs we can probably nail down what the issue is straight away. Positive the reason your request is failing is due to a different reason! With the above in mind, id suggest you double check the error youre getting, cos it doesnt make sense that your endpoint isnt expecting the colon to be % encoded. http, ftp, etc.) from the server portion of your request. The colon character is used to separate the protocol (e.g. Its the same as say the ? (indicates the end of the Template parameters and beginning of the Query and Matrix portion of the URI string) and / character (separators in your URI string before the query string). The reason i ask is that the RFCs that discuss % encoding indicate that a colon is reserved character and has special meaning in URLs. Hey behaviour is srandard and i wouldn't expect anything else.any http request which contains a colon char in a parm value is % encoded like this.Are you sure the error you are seeing is from % encoding your colon : character?
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |