Forum Discussion
9 Replies
Sort By
- hooleylistCirrostratusHi Kirit,
- Kirit_Patel_521NimbostratusAaron
- hooleylistCirrostratusThe HTTP traffic should be proxied through to the pool regardless of the method.
- HamishCirrocumulusUmm... What do you get back?
when CLIENT_ACCEPTED { Enable HTTP processing for all requests by default HTTP::enable } when HTTP_REQUEST { selectively disable HTTP processing for specific request methods switch [HTTP::method] { "MOVE" - "COPY" - "LOCK" - "UNLOCK" - "PROPFIND" - "PROPPATCH" - "MKCOL" { HTTP::disable } } }
- hooleylistCirrostratusPer SOL7581 that was fixed ages ago, so I think DELETEs should be handled fine with an HTTP profile enabled on any recent version.
- L4L7_53191Nimbostratus@Hamish: this problem may be solved already, but I really like that rule! Nice one.
- hooleylistCirrostratusI always cringed when I see HTTP::disable as it disables the HTTP filter for the rest of the TCP connection. So even if you can't put the current request/response through the HTTP proxy for some reason, you don't get any further HTTP events (or HTTP load balancing, persistence, etc) for the life of the connection. I wish there was a simple way to detect the end of the next HTTP response and automatically re-enable the HTTP filter.
- HamishCirrocumulusYeah.
- hooleylistCirrostratusThat's a good option. I'll add that to the HTTP::disable wiki page :)