Problem/Motivation

The outbound requests from Akamai to clear a cache via the EdgeGrid client does not take into account the Drupal settings array for http_client_config.

Steps to reproduce

We have found that our server, deployed in a DMZ does not send its requests out thru the proxy, but rather the unproxied route, which is then blocked, causing the request to time out.

Proposed resolution

Instead of instantiating the client config as an empty array, use the Drupal settings array for http_client_config.

Remaining tasks

User interface changes

n/a

API changes

n/a

Data model changes

Issue fork akamai-3365204

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

Comments

elgordogrande created an issue. See original summary.

elgordogrande’s picture

StatusFileSize
new931 bytes
moshe weitzman’s picture

thanks. can you see if any similar change is needed for 5.x branch?

moshe weitzman’s picture

Status: Active » Needs work
kwasib’s picture

Yes, this change is needed for 5.x. I recently encountered this problem and successfully applied the patch (with fuzz) in a test environment to fix it.

mschudders made their first commit to this issue’s fork.

mschudders changed the visibility of the branch 3365204-use-httpclientconfig-proxy to hidden.

mschudders’s picture

Status: Needs work » Needs review

https://git.drupalcode.org/project/akamai/-/merge_requests/31

MR31 is a reroll against the latest code.

  • smustgrave committed 6ae0620e on 6.0.x
    feat: #3365204 Use http_client_config proxy settings for clearing
    
    By:...
smustgrave’s picture

Version: 4.1.0 » 6.0.x-dev
Status: Needs review » Fixed

Since it's a feature request and pretty minor going to include in 6.0.x

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.