https://issues.apache.org/bugzilla/show_bug.cgi?id=50328
--- Comment #8 from Nick Kew <[email protected]> 2012-01-16 13:20:16 UTC --- 1. I just looked. It seems TraceEnable is allowed in a VirtualHost context, which leaves scope for configuration errors. Anyone who gets this should perhaps start by checking TraceEnable Off is set at top-level. 2. Comment #5, unlike the original report, looks like valid HTTP. I just spotted that today. I think there could be a real bug here: ap_send_http_trace is a map_to_storage hook with priority APR_HOOK_MIDDLE. map_to_storage is RUN_FIRST, which opens the possibility of never checking for TraceEnable if another module gets in first. And we could already be in an errordocument before we hit map_to_storage. If someone can post an actual config that provokes this, please reopen. Though the apparent bug is nothing to do with TraceEnable, rather it's the TRACE method being treated as a regular GET/HEAD. -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
