On Wed, Mar 21, 2012 at 16:23, Reindl Harald <h.rei...@thelounge.net> wrote: > Am 21.03.2012 21:02, schrieb Greg Stein: >> On Wed, Mar 21, 2012 at 15:59, Mark Montague <m...@catseye.org> wrote: >>> On March 21, 2012 15:33 , "Roy T. Fielding" <field...@gbiv.com> wrote: >>>> >>>> TRACE won't work at all if the most popular end-point doesn't support it. >>> >>> Why would this be a bad thing? Or, to phrase it another way, what are the >>> situations in which it is desirable that TRACE be already-enabled on a web >>> server as opposed to having the owner of the web server enable the TRACE >>> method in response to a specific debugging need? >> >> Roy means that if we don't set the precedent for TRACE being present >> and how it is supposed to work, then nobody else will. The Apache HTTP >> server is effectively the embodiment and leader of the HTTP >> specification. > > and now tell us ONE real world reason to > enable it BY DEFAULT
Don't get ALL-CAPS angry at me. There's no call for that. It just seemed that Mark wasn't understanding Roy's comment, so I tried to elucidate. -g
