Whitespace support removal Q/A
(Doc ID 3034550.1)
Last updated on OCTOBER 02, 2024
Applies to:
Oracle Fusion Cloud Field ServiceInformation in this document applies to any platform.
Purpose
This document answers common questions from customers about what are the impacts to their organization with the announcement of the whitespace support removal announced to take place on 19-November-2024*, as per a correspondence that has been sent out:
We are writing to inform you that according to the IETF Internet Standards, all non-encoded URL whitespaces are considered unsafe.
Therefore, all Oracle Field Service Cloud requests (including APIs) containing non-encoded whitespaces in URLs will be rejected starting on 19-November-2024.
When attempting to connect to any Oracle Field Service Cloud endpoint, including API and web interface, using non-encoded whitespaces in URLs will result in a 400 response code.
Connecting through browsers will work as usual as all browsers encode whitespaces in URLs by default.
* Please note that the original date (1-Aug-2024) has been postponed and the new date is 19-November-2024.
Questions and Answers
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Purpose |
| Questions and Answers |
| Q: What is the impact of this change on OFS ? |
| Q: What are the changes required to be prepared for when this restriction becomes effective ? |
| Q: Will the changes be rolled out in lower environments prior to being pushed to production ? |
| Q: Can you provide any occurrences where our environment is including these Whitespaces? |
| Q: Is a rollback possible after the change? |