Hello, My setup: remote server: -I have a universal forwarder setup on a GlassFish server. splunk server (Splunk 4.2): -I have free splunk setup to only communicate on 127.0.0.1 -I have iPlanet WS7 installed and acting as a reverse proxy --I have two virtual servers setup, one to handle the web interface and one to handle the forwarder communication Now my issue is that the request getting sent to splunk via the forwarder are returning with a 400 status code and the message "--splunk-cooked-mode-v2--". Has anyone used a similar setup? and if so how did you handle your forwarder communication? I was thinking I could setup a light forwarder splunk instance on my server that proxies the data between my external ip and my internal ip, but I would like a cleaner solution (i.e. using my iPlanet WebServer). When proxying forwarder communication via a reverse proxy are there any settings I should be aware of and might be missing? Should I be rewriting some of the headers, change forwarder paramaters ...etc ? Thanks Rob ... View more