Anne van Kesteren wrote:
Well, magic is quite scary, I'd rather have a statement explaining
roughly what TRACK is about (something non standard, not well
documented, and quite similar in functionnality to TRACE).
The specification says "Note: TRACK poses a security issue to legacy
server deployments." What is not good about that?
TRACK is specific to a legacy version of IIS, and not documented
anywhere (right?).
So, I think the proper way to deal with this is either to be silent, or
to add this as an implementor's note in an appendix.
Requiring implementors to put in workarounds for something that is
neither documented nor shipping in current server versions is really
hard to accept.
BR, Julian
