Hi Conny,
The RFC states that it must return the allowed methods, but I think it is not correct to return some generic values from a hidden device between the requester and the service. I think the current implementation is in violation with the (meaning of the) RFC.
I create a service on the gateway that only allows the POST method. The requester use a trace and gets a response that he cannot use the TRACE method but could use PUT, DELETE e.d., but when he tries this it gives him an exception. He should be confused.
Why is the TRACE method implemented in another way than the other methods?
Why do the other methods not conform the same RFC and return a 405 and must we build some custom handling to conform the RFC?