wp-media / wp-media/imagify-plugin

Improved Popup Message For Blocked Self-requests Due to Firewall, HTTP Auth, Etc

Open
#636 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

priority: medium type: enhancement UI
Dominant language
PHP
Stars
82
Forks
31
Avg merge
5d 10h
Merged PRs (30d)
9

Description

When the self-requests for optimization are being blocked by a user's server due to firewall setting, HTTP authentication, security plugin, or something similar, Imagify Tools shows something like this (though the error codes can also be 401 or 403):

image
image
image

We could offer a popup informing users this is the cause and linking to possible solutions:

image

The code below links to the same Optimization is Stuck page as we do for cURL Error 28 / timeout issues, and we could add a section to it specifically for these cases with suggestions like:

• Whitelist 51.68.166.142 with the server or possibly security plugins

• Use the following in wp-config.php if site is behind HTTP authentication:

define( 'IMAGIFY_AUTH_USER', 'your_auth_username_here' );
define( 'IMAGIFY_AUTH_PASSWORD', 'your_auth_password_here' );

• Disable security plugin

Or we could create a new page with these suggestions, whatever the team thinks is the best option.

<div id="swal2-content" class="swal2-content" style="display: block;">A firewall, server setting, HTTP Authentication, or security plugin is preventing image optimization. <a href="https://imagify.io/documentation/optimization-is-stuck/" rel="noopener" target="_blank">More info and possible solutions</a>.</div>

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the Imagify Tools handling for blocked self-requests and the existing cURL Error 28/timeout popup. Confirm how HTTP 401, 403, and firewall-related failures are surfaced, then update the popup and the Optimization is Stuck documentation with the agreed guidance; done means affected users see the explanatory message and a working help link.

Written by the indexing model from the issue text.

Assessment

Tech stack
php, wordpress
Domain
backend, frontend
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.