Forum Discussion

Andy_V_137639's avatar
Andy_V_137639
Icon for Nimbostratus rankNimbostratus
Nov 13, 2013

Getting around CORS with IRULES

Our website uses AJAX requests that makes requests from a page delivered from VIP A (www.acmecorp.com) to send requests to VIP B (api.acmecorp.com). We had to go ahead and put in a bunch of headers ...
application delivery
deployment
devops
iRules
  • Simon_Kowallik1's avatar
    Simon_Kowallik1
    Nov 13, 2013

    you can use the ProxyPassV10 irule for this.

     

    your datagroup content would look like this: www.acmecorp.com/api/ api.acmecorp.com/ pool_api_servers

     

    the virtual server's default pool should be the one for the www.acmecorp.com servers and you must use a oneconnect profile in the VS as well.

     

    the proxypass irule will rewrite any request going to www.acmecorp.com/api/XYZ to api.acmecorp.com/XYZ and send it to the pool pool_api_servers proxypass will also take care of the location header in http redirects and rewrite it for you.

     

Kevin_Stewart's avatar
Kevin_Stewart
Icon for Employee rankEmployee
Nov 14, 2013

If I may add, if I understand you correctly, the Ajax is a client side thing. Script in the response content from www.acmecorp.com causes the client to make an Ajax call to api.acmecorp.com, but the client's firewall is stripping out the headers that are allowing this cross origin request to happen. So instead of the client making the request, you want the www.acmecorp.com VIP to make the request. If that's true, then I think you were on the right track to begin with, with a few modifications:

when HTTP_REQUEST {
    if { [string tolower [HTTP::uri]] starts_with "/api" } {
        HTTP::header replace Host "api.acmecorp.com"
        HTTP::uri [string map {"/api" ""} [HTTP::uri]]
        virtual API_VIP
    }
}

This will cause all "/api" requests to swing over to the API_VIP virtual server with the appropriate Host header and URI.