Storm Heg
Storm Heg
@jefftriplett according to Heroku support, the [IP addresses used are highly dynamic and the IP ranges cover whole AWS regions](https://help.heroku.com/JS13Y78I/i-need-to-add-heroku-dynos-to-our-allowlist-what-are-ip-address-ranges-in-use-at-heroku) - whitelisting doesn't sound like it would help both of...
@jefftriplett no dice, still 403'ing curl -I https://djangopackages.org/api/v4/grids/?q=wagtail ``` HTTP/2 403 date: Fri, 14 Mar 2025 13:34:50 GMT content-type: text/html; charset=UTF-8 accept-ch: Sec-CH-UA-Bitness, Sec-CH-UA-Arch, Sec-CH-UA-Full-Version, Sec-CH-UA-Mobile, Sec-CH-UA-Model, Sec-CH-UA-Platform-Version, Sec-CH-UA-Full-Version-List, Sec-CH-UA-Platform,...
No dice, still 403 (Dyno has a completely different IP address this time - indeed very dynamic)
@jefftriplett from this line onwards https://github.com/wagtail/wagtail.org/blob/a5e5aac8a5e46ba1a2d69af9d54f364518197ec9/wagtailio/packages/views.py#L12
@jefftriplett have you tried making the request from an AWS ip range?
@jefftriplett still not - please lets go with an alternative
I'm going to revisit this when Wagtail 6.3 is released and add support for it as well. Thanks for the review @mgax 👍
I think this is ready for another round of review - if you are available - @mgax!
It looks like custom extension policies have shipped with cryptography 45 last week. Would love to see this land 😃
I tried uploading this file and can confirm I'm seeing the same error (`Willow==1.8.0` and `wagtail==6.2.1`)