> When you mean going through a proxy do you mean a web proxy (i.e. squid). I > had > trouble building a script using perl and the Spacewalk API to go through a web > proxy to reach the Spacewalk Server amd the RHN Network.
proxy being spacewalk proxy - its odd as my perl script works on my test system via a proxy but not in my production setup when using a proxy, directly to the server is fine. On the test system that works i see this on the proxy logs.... 192.168.122.3 - - [27/Jul/2010:21:13:23 +0000] "POST /rpc/api HTTP/1.1" 200 334 "-" "libwww-perl/5.805" 192.168.122.3 - - [27/Jul/2010:21:14:52 +0000] "POST /rpc/api HTTP/1.1" 200 170 "-" "libwww-perl/5.805" 192.168.122.3 - - [27/Jul/2010:21:14:52 +0000] "POST /rpc/api HTTP/1.1" 200 751 "-" "libwww-perl/5.805" 192.168.122.3 - - [27/Jul/2010:21:14:52 +0000] "POST /rpc/api HTTP/1.1" 200 128 "-" "libwww-perl/5.805" 192.168.122.3 - - [27/Jul/2010:21:14:53 +0000] "POST /rpc/api HTTP/1.1" 200 128 "-" "libwww-perl/5.805" but on the production system through a proxy to the production spacewalk it fails. Logs say 10.10.10.10 - - [27/Jul/2010:21:19:40 +0000] "POST /rpc/api HTTP/1.1" 200 173 "-" "libwww-perl/5.805" 10.10.10.10 - - [27/Jul/2010:21:19:40 +0000] "POST /rpc/api HTTP/1.1" 200 - "-" "libwww-perl/5.805" and the client reports # perl /usr/local/bin/swregcheck.pl 500 EOF when chunk header expected Clients can register and get updates through the proxy fine so i am a bit stumped. I was going to try the python route, but to be fair i am clutching at straws thanks _______________________________________________ Spacewalk-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/spacewalk-list
