* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com

* Podcasts
* Social Channels
* Video Streaming

 

 

 

 

 

ABOUT DEVCENTRAL

DevCentral News Technical Forum Technical Articles Technical CrowdSRC Community Guidelines DevCentral EULA Get a Developer Lab License Become a DevCentral MVP

RESOURCES

Product Documentation White Papers Glossary Customer Stories Webinars Free Online Courses F5 Certification LearnF5 Training

SUPPORT

Manage Subscriptions Professional Services Professional Services Create a Service Request Software Downloads Support Portal

PARTNERS

Find a Reseller Partner Technology Alliances Become an F5 Partner Login to Partner Central

---

©2024 F5, Inc. All rights reserved.

We have several load balancers configured on this F5 using the following irule:

when HTTP_REQUEST { \n switch -glob [HTTP::uri] { \n \"Redacted URI\" { return }\n \"Redacted URI\" { return }\n \"Redacted URI\" { return }\n \"Redacted URI\" { return }\n \"Redacted URI\" { return }\n default { HTTP::redirect https://[getfield [HTTP::host] \":\" 1][HTTP::uri] }\n } \n}

This is applied to the HTTP Virtual server which successfully redirects all incoming requests that are HTTP to the HTTPS virtual server.

What we are needing now is a way to exempt the above from happening in the event that the virtual server with all of the ssl profiles does not actually have an SSL profile for the requested URI.

Outside of writing in an exemption for each URI, is there a way to look at the virtual server and verify the incoming URI does or does not have an ssl profile applied on the other virtual server?

We have several load balancers configured on this F5 using the following irule:

when HTTP_REQUEST { \n switch -glob [HTTP::uri] { \n \"Redacted URI\" { return }\n \"Redacted URI\" { return }\n \"Redacted URI\" { return }\n \"Redacted URI\" { return }\n \"Redacted URI\" { return }\n default { HTTP::redirect https://[getfield [HTTP::host] \":\" 1][HTTP::uri] }\n } \n}

This is applied to the HTTP Virtual server which successfully redirects all incoming requests that are HTTP to the HTTPS virtual server.

What we are needing now is a way to exempt the above from happening in the event that the virtual server with all of the ssl profiles does not actually have an SSL profile for the requested URI.

Outside of writing in an exemption for each URI, is there a way to look at the virtual server and verify the incoming URI does or does not have an ssl profile applied on the other virtual server?

The F5 Certification is excited to announce that all five of the NEW F5 Certified BIG-IP Administrator Certification (F5 CAB) exams are now live and available to schedule via the new Education Services Portal.

I believe this may work:

when HTTP_REQUEST { \nif { [SSL::mode] == 0} { HTTP::redirect http://[HTTP::host][HTTP::uri]}\n}\n

I'm not sure that's what I'm looking for.

I already have the redirect working for everything that is http to be redirected as HTTPS.

What I need now is basically an exemption mechanism where if the request comes in, and there's no SSL profile for that URL, then to let it go through as HTTP.

I believe this may work:

when HTTP_REQUEST { \nif { [SSL::mode] == 0} { HTTP::redirect http://[HTTP::host][HTTP::uri]}\n}\n

I'm not sure that's what I'm looking for.

I already have the redirect working for everything that is http to be redirected as HTTPS.

What I need now is basically an exemption mechanism where if the request comes in, and there's no SSL profile for that URL, then to let it go through as HTTP.

Is there like a:

if URI match Profile redirect

else return

You can put your list of the virtual servers without an SSL profile applied in a data group and check the incoming request against that.