ProxySG & Advanced Secure Gateway

 View Only
  • 1.  Akamai User Agent authentication

    Posted Oct 09, 2017 11:59 AM

    I've found some old CPL in one of my policies, and need to understand it better.

    it's labeled "Akamai Chunking - KB3817", and commented "Policy used to disable authentication for Akamai user agents"

    It says :

    <Proxy>
        request.header.User-Agent="^Akamai*" authenticate(no)
    ; Policy to disable http client and server persistence and protocol detection when Akamai user agent is found.
    <proxy>
    request.header.User-Agent = '^Akamai*' http.client.persistence(no) http.server.persistence(no) detect_protocol(no) Allow
    ; Policy to disable caching, pipelining and to use HTTP 1.0 instead of 1.1
    <cache>
    request.header.User-Agent = '^Akamai*' cache(no) pipeline(no) http.request.version(1.0)

     

    Searches for KB3817 and 'Akamai user agent' are dead-ends.

    I suspect it's historical junk, but want to be confident before I delete it.

    Can anybody shed any light on whether this CPL is still relevant?

    Thanks!



  • 2.  RE: Akamai User Agent authentication
    Best Answer

    Posted Oct 10, 2017 06:11 AM

    Hi Ferwerda,

     

                Saw your other post too. I have not seen this in production for sometime now. May be added to your boxes when Akamai agents were being troubleshooted for some issues. The 3 polices combined to for the Magic rule we add for testing access issues. All these 3 are not required to fix the issue. I will say, to remove this and test the access for any Akamai based links for problem. If none found, make the removal permanent.



  • 3.  RE: Akamai User Agent authentication

    Posted Oct 12, 2017 11:33 AM

    Thanks Aravind,

    I will delete and test as you recommend.

    Much appreciate your feedback.