Oracle Request Enhancements

[cschuchardt88]

Summary or problem description
Change Oracle to use HTTP OPTIONS before it gets the URL to see what the options are for the URL. So oracle knows how to call the URL. If the only HTTP option is for example POST then oracle should use a POST request to fetch the URL. Should Support GET, POST, PUT, and DELETE. If multiple options are set than it should default to GET request.

Where in the software does this update applies to?

• Plugins

[roman-khimov]

Should Support GET, POST, PUT, and DELETE

#1980

[cschuchardt88]

I think if oracle's do OPTION requests 1st to determine the verb types. Then we wouldn't have to worry about multiple oracle servers posting data to a server. If all match than from the OPTION request. Then get the accepted verb. And if more then one verb is defined than do GET request. Unless we add an option for different verbs in the oracle native contract. Or even better oracle passes a unique ID to the server that the server can verify somehow. So that the requesting server can know its a valid oracle, and then if more than one request comes in. The server will just sends back the already processed data.

For example oracle sends a HEADER that is a signature of the URL with the POST.

Header would be:
Oracle-Req: <signature format>=<signature>

Signature would be:
verion=<oracle version>;request=<url>;<data format>=<data>

Would that be doable?

[Jim8y]

�Well, this is irellevent to this issue, but, @roman-khimov how come you can remember every single issue and pr in the whole neo projects,,,,