User feed is not available and return an 500 internal server error

[llaville]

Hello,

On PEAR website source code https://github.com/pear/pearweb/blob/master/public_html/feeds/feeds.php#L147
user feed is accepted and produce results such as

• https://pear.php.net/feeds/user_jon.rss [OK]

wget --save-headers https://pear.php.net/feeds/user_jon.rss

--2024-04-14 14:12:52--  https://pear.php.net/feeds/user_jon.rss
Resolving pear.php.net (pear.php.net)... 109.203.101.62
Connecting to pear.php.net (pear.php.net)|109.203.101.62|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 5877 (5.7K) [text/xml]
Saving to: ‘user_jon.rss’

user_jon.rss                        100%[===================================================================>]   5.74K  --.-KB/s    in 0s

2024-04-14 14:12:53 (42.5 MB/s) - ‘user_jon.rss’ saved [5877/5877]

With user_json.rss chunk of contents

HTTP/1.1 200 OK
Date: Sun, 14 Apr 2024 14:12:53 GMT
Server: Apache
Vary: Accept-Encoding
X-Frame-Options: sameorigin
X-XSS-Protection: 1; mode=block
Strict-Transport-Security: max-age=31536000
Content-Length: 5877
Keep-Alive: timeout=5, max=100
Connection: Keep-Alive
Content-Type: text/xml; charset=iso-8859-1

<?xml version="1.0" encoding="iso-8859-1"?>
<rdf:RDF
    xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
    xmlns="http://purl.org/rss/1.0/"
    xmlns:content="http://purl.org/rss/1.0/modules/content/"
    xmlns:dc="http://purl.org/dc/elements/1.1/"
>

< lot more >

But on PECL website, source code https://github.com/php/web-pecl/blob/master/public_html/feeds/feeds.php#L56
user feed is implemented but lead to an internal server error

wget --save-headers https://pecl.php.net/feeds/user_derick.rss

--2024-04-14 04:17:25--  https://pecl.php.net/feeds/user_derick.rss
Resolving pecl.php.net (pecl.php.net)... 104.236.228.160
Connecting to pecl.php.net (pecl.php.net)|104.236.228.160|:443... connected.
HTTP request sent, awaiting response... 500 Internal Server Error
2024-04-14 04:17:30 ERROR 500: Internal Server Error.

[derickr]

This should now be fixed, once the website's code updates.

[llaville]

@derickr Thanks a lot !