Hi @RenzoDani02 - I also faced this issue, and saw that there also was an issue filed with OpenLayers a few months ago. If memory serves (it doesn't often), I recall old ArcGIS REST documentation specifying that these fields should be UPPER-CASE, justifying why OpenLayers decided at the time to enforce UPPER-CASE, so I have worries that there may still be ArcServers running an old ArcREST that requires those, and that updating OpenLayers to assume lower case may be backward incompatible (not to mention bizarre behavior for anyone who sets some of the automatically populated fields manually).
NOTE: If anyone can confirm that ALL-CAPS for BBOX was ever required and can point me at the docs, I would be extremely grateful!
However, I wrote a patch for OpenLayers because:
- I don't expect Esri to roll out a fix for this backwards-incompatible bug soon
- Even if they do, how long will it be before everyone who adopted this version upgrades to one without this regression?
- I don't actually know if any ArcREST instances still exist that would require ALL CAPS (if there ever were any)
The good news: OpenLayers has accepted my patch - You can either compile the current main branch yourself, or wait for the next version to be released (there seems to be a new release every few months).
Hope this helps!
