wp-media / wp-media/imagify-plugin
Picture method uses http instead of https in docker container worpress
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 82
- Forks
- 31
- Avg merge
- 5d 10h
- Merged PRs (30d)
- 9
Description
Using the Webp “picture”, delivered images are shown as “insecure content”.
webp images are delivered using http instead of https
Site is deployed in a container instance that is default exposed as 80 http, cloudflare in the middle rewrites all http to https
wp database and all urls are set to https://
I suspect the pluging retrieves the request, since the request cames from cloudflare as http, plugin delivers http urls instead https.
Is there a configuration to change the deliver behavior of webp images?
Can some developer could give hints where to change the option to submit a PR to append the option
docker-image: bitnami/wordpress-nginx
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the WebP picture behavior with bitnami/wordpress-nginx behind Cloudflare, checking whether requests reaching the container use HTTP while the site URLs use HTTPS. Trace how the plugin builds WebP image URLs and verify that the completed fix produces HTTPS URLs without mixed-content warnings.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, php, wordpress
- Domain
- backend, security, web-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100