Forum Discussion
mmelber14_62984
Nimbostratus
NimbostratusHTTP VS/FASTL4 VS and an iRule
Hello,
We are loadbalancing a family of websites behind a Virtual server that was orginally setup as a standard VS via port 80. This configuration did not work due to the fact that we were seeing a massive amount of client aborts and content not being served back to the clients. We swtiched to a FastL4 VS which source address affinity persistence and that gave us the results we were looking for. The biggest issue is we need to preserve and pass the client source IP address back to the servers for logging purposes. I researched the X-forwarded-for header insert and realized that it does not work since we are in a FastL4 setup. Is there a way we can make this entry work with our current FastL4 VS or is there a way that we can strip an http profile completely to only use the x-forwarded-for option? The error message we were receiving when a standard VS and performanceHTTP VS were used was this: http_process_state_prepend - Invalid action EV_INGRESS_DATA during ST_HTTP_PREPEND_HEADERS (Server side: vip= profile= pool=)
I reviewed knowledgebase article sol5922: Error Message: http_process_state_prepend - Invalid action EV_INGRESS_DATA during ST_HTTP_PREPEND_HEADERS and made the applicable changes. We still encountered client aborts and content that was not being served.
Thanks for your time and help!
1 Reply
hoolioCirrostratus
Hi,
I didn't think you could add an HTTP profile to a Performance L4 VS with a FastL4 profile. The idea of the FastL4 VS is that you skip any layer 7 processing. So the idea of manipulating HTTP headers on a FastL4 virtual doesn't work.
You might try setting up a test standard virtual server with a custom HTTP profile in order to troubleshoot the original issue. Once you resolve that you could change the production virtual server configuration to a standard VS with a custom HTTP profile that inserts the XFF header.
Aaron
