Forum Discussion
Marissa_Kato_10
Nimbostratus
NimbostratusBigIP SSL proxy rule rejecting AJAX requests
BigIP SSL proxy rejecting AJAX requests:
I am currently using a rule to generate http traffic to redirect to https traffic i.e.
redirect to "https://%h/%u"
When this rule is applied along with its SSL proxy, it seems that functions using AJAX requests on the web page do not function properly under https traffic (For example: vehicle models do not load from its database). The AJAX requests only function WITHOUT the SSL proxy & rule, i.e. the vehicle models load properly ONLY under http traffic.
Is this syntax correct? Do I need to enter a different rule? Or, is this a web application issue?
So far, F5 support has not been able to help with this issue and I need to get an answer soon. In advance I'd appreciate any feedback.
3 Replies
- That's certainly the correct syntax for your rule. My first question would be..have you tested the same content under SSL encryption without going through the rule or even the BIG-IP?
This sounds like it's likely more due to the SSL than the BIG-IP and the rule's interaction.
Colin 
Marissa_Kato_10Colin,
I appreciate your response. I had been discouraged since I had not received a reply right away. However, in response to your message, the content has been tested under SSL encryption without going through the Big-IP and it works. Once we put it to go through the Big-IP the AJAX request is "rejected"/i.e. displays an error on the page.
We are anxious to get an answer on this soon! Is there any other rule or different setup to fix this? Do we need to change from F5 to a different load balancer OR will version 9 on a new platform resolve this issue?
Please advise. Your immediate response will be greatly appreciated.
Thanks,
Marissa- Marissa,
you'll need to open a case on the issue with F5 support. It appears that your problem will need deeper troubleshooting than we are able to provide in this forum. In order to help you, support will need packet captures of the traffic when the problem occurs along with configuration and logs from your BIG-IP (they will tell you exactly what information they need and how to get them). It is my guess that iRules are actually not the root cause.
