Thanks for the question, jeremy.
Asked: October 11, 2019 - 10:27 am UTC
Last updated: May 04, 2020 - 3:43 am UTC
Version: 19.1
Viewed 1000+ times
You Asked
Hi Tom,
I've been using Application Express to develop my application for 1 year. By the way I’d like to tell you how much Ask Tom has been useful for me to understand the way Apex is working and I’m very grateful to you guys who are devoted to help people resolving issues.
I set up a Restful service module to receive JSON data, using GET and POST Methods on ORDS.
It was working well, allowing my DB to insert into tables thanks to POST method, using PL/SQL blocks on POST endpoints.
>>> the following message has been placed on apex.oracle.com on 21st september 2019:
"apex.oracle.com was recently migrated to new infrastructure"
I'm using apex on apex.oracle.com, not on my own site.
Now, I'm using 19.2 version of Application Express, still on apex.oracle.com
Everything was fine until the last migration that Oracle made 3 weeks ago, and my inserts suddently stopped on 21st of September. Now, POST method is not working anymore and when I’m testing it on my browser, it says “405 - Method not allowed”. But GET method is still working yet. I can even insert into tables using GET method, but not with POST method. I clarify that I didn't update anything on HTTP header or endpoints at anytime before and after migration.
I looked for any change that could occur in security settings (in Shared components) but I couldn't find any change comparing to how it was before migration.
I would like to launch this project on production in several weeks and I wonder if the issue is related to the fact that I’m actually using a free version of Apex, assuming that before the migration it was not a problem ? Or is there any parameter that I missed and should be done since this migration is done ?
I hope I gave you all the information you need to understand my issue.
Thank you for your help.
and Connor said...
Thanks for your patience.
I checked with the APEX team and they said nothing has changed in that area.
I also then created a workspace on apex.oracle.com myself and REST enabled a table to setup some endpoints.
By *default*, my automatically created points where PUT, GET and I had to manually create my POST endpoint. But once created, I had no problems running it.
One thing I did notice, was then when my PLSQL was incorrect, I sometimes got a spurious results of "Method not allowed" instead of the usual "Internal error". So double check your code to make sure privileges and usage are OK.
If all else fails, perhaps create a new sample workspace and reproduce the error there, and then put this on the apex forum (
https://apex.oracle.com/forum ) with the user/pass so the apex team can jump in and take a look.
Rating
(1 rating)
Is this answer out of date? If it is, please let us know via a Comment