Hi Chris, I had similar issue, here is my solution: Your redirect rule has to be 307 type (not 302) because of POST method used by WU clients. That may be why you can get the WSUS welcome pic (method GET) but not update your client (method GET and POST is used). Also, be carefull of BITS service used by WU clients, it may try to download update directly from your WSUS server and bypass your apache...You have to configure WinHTTP service with proxycfg if you want that all your WU traffic get through your apache. Hope this help you. Regards, Romain 2012/8/17 Yehuda Katz <yehuda@xxxxxxxxxx>: > Can you run something like wires hark and see exactly what the request was > when you got the 405? > (Sorry for top-posting. I am using a mobile device that does give me a > choice.) > > > On Thursday, August 16, 2012, Chris Arnold wrote: >> >> Apache2 2.12 (?) on sles11 sp2. We have a vhost file with the following >> rule: >> RewriteRule ^/$ http://192.168.123.2/ >> This rule points certain traffic to the ip for WSUS (windows software >> update services). The clients not using this rule work fine but the 2 that >> do use the rule fail with 405 error. I mention the whole WSUS thing to >> verify this is a rule/vhost error. >> I expect apache to send http://updates.domain.com traffic to the WSUS >> server. What we get are 405 (method not allowed). From one of these 2 PC's, >> I can goto http://updates.domain.com/ and get the WSUS welcome pic, so >> apache appears to be sending that traffic to the WSUS server. I have asked >> on the WSUS forums too. Any idea as to why 405's? >> >> Sent from my iPhone > > > > -- > Sent from a gizmo with a very small keyboard and hyper-active auto-correct. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|