[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Simulating SKS best practice [Was: is back running H

From: Andrew Gallagher
Subject: Simulating SKS best practice [Was: is back running Hockeypuck]
Date: Thu, 15 Apr 2021 12:33:44 +0100
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.9.0

On 23/03/2021 12:58, Andrew Gallagher wrote:
On 21/03/2021 21:48, Martin Dobrev wrote:
I had to play with mod_rewrite and force a redirect from //pks/lookup?op=stats&options=mr/ to //pks/lookup?op=stats /to let the script parse HTML. I don't have a proper explanation why peers and recon port are not picked from the produced JSON but left out (line 286/287).

I can confirm this works, and it has the unexpected side effect that is now recognised as SKS, even though it is still declaring itself Hockeypuck.

The following hockeypuck servers appear to have implemented a stats rewrite rule:

Could I humbly request of hockeypuck operators that this workaround be limited to's IP address? This would allow the machine-readable JSON to be read by other spiders which may or may not exist in the future... ;-) ;-) ;-)

For example, uses the following apache snippet:

RewriteCond %{REMOTE_ADDR} ^37\.191\.231\.105
RewriteCond %{QUERY_STRING} op=stats&options=mr
RewriteRule ^/pks/lookup [P,L]

Similarly, could we collectively agree to emit {software: "Hockeypuck"} and the real Hockeypuck version number when simulating SKS, so that the human-readable status is accurate? So long as "Hockeypuck" has a capital "H", the pool spider shouldn't reject you (it may reject you for other reasons, but not for running hockeypuck).

Thanks, everyone.

Andrew Gallagher

Attachment: OpenPGP_signature
Description: OpenPGP digital signature

reply via email to

[Prev in Thread] Current Thread [Next in Thread]