Irule to bypass http profile on APM VS

Gabriel,

As far as i know you can't enable/disable a http profile in an iRule as such (although some individual http profile options you can).

Hopefully your SE can give you a pointer on what part of the profile might be causing your issue.

Hope this helps,

N

Thanks for the quick reply, ya I don't know it feels like the http profile is built for web traffic/Apps, so when you try to run port 80 on a different app I would guess the app makes requests in a different way as opposed to a browser. Not really looking to disable the profile just bypass it for certain addresses.

The solution could be to forward specific traffic to another VS without HTTP profile. I do it for a application non RFC compliant.

when HTTP_REQUEST {
if {[HTTP::uri] starts_with "/company/Reports/"}
{
log local0. "Requete sur Report --> VS_nonHTTP"
virtual /Common/VS_nonHTTP
}
}

I don't know if it works in your use case, but that could help you out.

Matt

Thanks so much, can I do this?

when HTTP_REQUEST { if {[HTTP::uri] starts_with "chat.phl.com"}

Yeah or :

when HTTP_REQUEST { if {[HTTP::uri] contains "chat.phl.com"}
{
Log local0. "HTTP URI contains chat.phl.com"    
virtual /Common/VS_CHAT
}

And add this log iRule on the second VS (once without HTTP profile)

when CLIENT_ACCEPTED { log local0. "Connection on NON_HTTP VS"}

Don't forget to add ressources on the second VS (Pool and members). This VS can have any IP address. It doesn't matter because the connection comes from the first VS.

Hope this solution will works in your case. Else, enable logs on LTM and try to understand why HTTP profile meets an issue.

Whats the purpose of the second VS or why do I need two VS's?

You need one VS with an HTTP profile (which seems to meet an issue for you) and one another without. Basically, you need HTTP profile on VS1, I suppose, in order to start an APM session (Landing URI ...). If for any reason, you have an issue with this HTTP profile, the workaround is to forward to another VS without HTTP profile specific flow.

I had a similar issues and just disabled the http pofile in an irule for some non-compliant http. You could try the below. Would be interested in knowing if this works for others?

when HTTP_REQUEST { if {[HTTP::uri] starts_with "/company/Reports/"} { HTTP::disable } }