Hi Unifacers,
up to last week my Uniface REST DSPs were supporting HEAD, GET, POST, PUT, DELETE methods; now I would like to extend them to TRACE and OPTIONS.
I've added those new REQUEST_METHODs to my DSP sample but trying to request them I did NOT reach the DSP, because I presume Tomcat is directly answer me.
These are responses received:
Executing request with OPTIONS method:
OUTPUT - headers:
Server=Apache-Coyote/1.1Allow=GET, HEAD, POST, PUT, DELETE, TRACE, OPTIONSContent-Length=0Date=Sun, 18 Apr 2021 10:05:33 GMT
OUTPUT - content:
(empty)
OUTPUT - response:
HTTP/1.1 200 OK
Executing request with TRACE method:
OUTPUT - headers:
Server=Apache-Coyote/1.1Allow=HEAD, DELETE, POST, GET, OPTIONS, PUTContent-Length=0Date=Sun, 18 Apr 2021 10:05:19 GMT
OUTPUT - content:
(empty)
OUTPUT - response:
HTTP/1.1 405 Method Not Allowed
I see a sort of contradiction here: default OPTION method is telling me TRACE is allowed but if I request TRACE the answer is "405 - Method NOT Allowed". (???)
I have three questions to be answered:
Question #1: the contradiction found is a "feature"? If yes, why is it there?
Question #2: I would like in both methods to reach the DSP to generate a proper answer page. Is this approach correct? Any pitfall to be considered?
Question #3: I am NOT a great Tomcat expert; could someone point me to a documentation page or in the right direction to adapt the basic Uniface configuration to support what I would like to do?
Thanks in advance for any hint, tips or trick.
Regards,
Gianni