WPIntell

Source evidence

Not working

Purge Varnish Cache · support · 2020-12-06T02:05:00+00:00

Purge Varnish Cache plugin evidence original source source API
complaintsentiment
mediumseverity
0.92relevance
4replies
Evidence linked to opportunitycommercial context

Proof Health

Open evidence

Commercial opportunities need traceable source links before they are treated as build-worthy.

4 / 31 rows with source links

12.9% of this page's analysis has direct source links.

0 build-decision rows missing links

0 rows here require auditable proof before promotion.

27 rows with no attached evidence

0 rows have source counts but still need direct links.

Conversation

support
RMvalues unresolved
Hi, The plugin installed and proper configured but it’s not working. My hosting developer checked and found 2 errors in class_purge_varnish.php Line 22 const PURGE_VARNISH_DEFAULT_TREMINAL = ‘127.0.0.1:6082’; You have defaulted the port to 6082, while some hosting environment may have use other port(s) Besides, there was an extra information in Line 147 Original $pack = $challenge . “\x0A” . $secret . “\x0A” . $challenge . “\x0A”; Edited $pack = $challenge . “\x0A” . $secret . $challenge . “\x0A”; Now it works. Please verify from your end. Thanks. Thank you! rmvalues Hi, I’m the developer. Here’s an excerpt from varnishadm command’s source (S_fd is the fd of the varnish.key file): SHA256_Update(&ctx, challenge, 32); SHA256_Update(&ctx, "\n", 1); do { i = read(S_fd, buf, sizeof buf); if (i > 0) SHA256_Update(&ctx, buf, i); } while (i > 0); SHA256_Update(&ctx, challenge, 32); SHA256_Update(&ctx, "\n", 1); As you can see there’s no \n after the secret key. Your plugin’s original implementation implies that there’s a trailing \n after the secret. This is not true in all cases, so IMHO you should follow varnishadm’s implementation Hello, I am varnish 6.5.1 + Ubuntu 20.04. Previously I cannot use plugin, it always says: The Varnish control terminal is not responding at 127.0.0.1:6082 Only I change line 147 of purge_varnish.php, it says: Status: Server OK: 127.0.0.1:6082 Varnish running. Documentation is not always correct/updated? I think it is not very rare for varnish. 🙂 This reply was modified 5 years, 5 months ago by meken . @strkol This is the only working varnish plugin for varnish 6.5, after @rmvalues change on 147 (“”). Thank you all! Do you have plan to fix this small “bug”?

Comments

4 shown
meken 2020-12-06T02:13:00+00:00

Thank you! rmvalues

strkol 2020-12-06T15:25:00+00:00

Hi, I’m the developer. Here’s an excerpt from varnishadm command’s source (S_fd is the fd of the varnish.key file): SHA256_Update(&ctx, challenge, 32); SHA256_Update(&ctx, "\n", 1); do { i = read(S_fd, buf, sizeof buf); if (i > 0) SHA256_Update(&ctx, buf, i); } while (i > 0); SHA256_Update(&ctx, challenge, 32); SHA256_Update(&ctx, "\n", 1); As you can see there’s no \n after the secret key. Your plugin’s original implementation implies that there’s a trailing \n after the secret. This is not true in all cases, so IMHO you should follow varnishadm’s implementation

meken 2020-12-06T16:32:00+00:00

Hello, I am varnish 6.5.1 + Ubuntu 20.04. Previously I cannot use plugin, it always says: The Varnish control terminal is not responding at 127.0.0.1:6082 Only I change line 147 of purge_varnish.php, it says: Status: Server OK: 127.0.0.1:6082 Varnish running. Documentation is not always correct/updated? I think it is not very rare for varnish. 🙂 This reply was modified 5 years, 5 months ago by meken .

meken 2021-01-28T06:05:00+00:00

@strkol This is the only working varnish plugin for varnish 6.5, after @rmvalues change on 147 (“”). Thank you all! Do you have plan to fix this small “bug”?