Skip to Main Content

ORDS, SODA & JSON in the Database

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

ORDS 18.2 + Tomcat 7/8 problem RFC 7230 and RFC 3986

Olafur TAug 17 2018 — edited Sep 3 2018

We just updated our test environment to ORDS 18.2 and APEX 18.1. As expected, APEX REST services are read-only.

But we are running unto a problem migrating the APEX REST services to ORDS.

So in the modal window "APEX REST Migration Warning" when I press "Migrate" the next page is a 400 error that I trace to Tomcat.

From the catalina.out: java.lang.IllegalArgumentException: Invalid character found in the request target. The valid characters are defined in RFC 7230 and RFC 3986

Looking at the URL there are letters that are nonconformant to those RFC's.

&success_msg=QVBFWCBiYXNlZCBSRVNUZnVsIHNlcnZpY2VzIGhhdmUgYmVlbiBtaWdyYXRlZC4g{}Q2hlY2sgdGhlIE9SRFMgUkVTVGZ1bCBzZXJ2aWNlcyBjb25zb2xlLg,,/i0alrVuoGy8I9E_bLXguBWaTMQNatGX1u8ftXI4Nrgu8IfCf3E9j1dgjRL-pEizpdgUWNSOvCliQZs9MHeHMVQ

If I take a normal letter out (B for instance) I get the 400 error. If I take out "{}" Tomcat allows it and APEX gives me a "Success message checksum error" so it seems to be the "{}" fault.

Any way to get passed this?

Best Regards

Olafur

This post has been answered by Olafur T on Aug 17 2018
Jump to Answer
Comments
Locked Post
New comments cannot be posted to this locked post.
Post Details
Locked on Oct 1 2018
Added on Aug 17 2018
3 comments
3,533 views