From: dbatty on
We have an application on CF5 that we have put behind a SSL proxy server. We
have go everything to work fine except we are running into time were we are
unable to read http header variables. Once you log into the SSL side, the
request along with header is sent to the cf5 server. We process, and send back
to the proxy to be sent back to the user. There is a HTTP_IV_USER variable in
the header that includes their login ID. We chneck that or display it in our
app using <CFOUTPUT>#HTTP_IV_USER</CFOUTPUT>. From time to time, users will
get the error that the variable did not exist. But a network packet capture
shows it existed when the packet came into the server. Can anyone help as to
why this works intermittently?

From: Ian Skinner on
I do not know if this would matter or not, but should that variable be
scoped? CGI.HTTP_IV_USER perhaps?

dbatty wrote:
> We have an application on CF5 that we have put behind a SSL proxy server. We
> have go everything to work fine except we are running into time were we are
> unable to read http header variables. Once you log into the SSL side, the
> request along with header is sent to the cf5 server. We process, and send back
> to the proxy to be sent back to the user. There is a HTTP_IV_USER variable in
> the header that includes their login ID. We chneck that or display it in our
> app using <CFOUTPUT>#HTTP_IV_USER</CFOUTPUT>. From time to time, users will
> get the error that the variable did not exist. But a network packet capture
> shows it existed when the packet came into the server. Can anyone help as to
> why this works intermittently?
>
From: dbatty on
We have tried scoping with CGI. and still the variable is hit or miss when you
do cfif's or cfoutputs. Keep in mind that every single time, the network
captures show the variable is there everytime it comes into the server. Any
other ideas?