bukka
Repos
51
Followers
191
Following
7

Events

Clarify removal of TC

Co-authored-by: Larry Garfield larry@garfieldtech.com

Created at 4 hours ago

Update TC vote

Co-authored-by: Larry Garfield larry@garfieldtech.com

Created at 4 hours ago

Clarify vacancies

Co-authored-by: Larry Garfield larry@garfieldtech.com

Created at 4 hours ago
issue comment
json_encode/decode simd by default?

I have been actaully looking into this and we cannot really use simdjson lib in its current form. It is not fully compatible and we will need some tweaks there. My plan is to eventually replace the current parser with something close to simdjson but will be probably more a C port of that. This is something that I plan to look after JsonSchema integration which will take some time so this will take even longer. In the meantime you can just use https://pecl.php.net/package/simdjson .

Created at 1 day ago
issue comment
Error compilling

You should not be mixing different versions of libraries as it might result in issues if this is just not for some testing. Ideally you should also recompile other libraries and use the same version for all. That's why it is usually easier to rely on system lib...

Created at 1 day ago
issue comment
Error compilling

LibreSSL is still supported. This looks like some mix up in settings. What you should be really using is pkgconfig. Just change it's path to your custom library build lib/pkgconfig or lib64/pkgconfig dir.

For example if you OpenSSL 1.1.1 is installed in /usr/local/ssl111, then you would do this

export PKG_CONFIG_PATH=/usr/local/ssl111/lib/pkgconfig

For OpenSSL 3.0 installed in /usr/local/ssl30, it would be

export PKG_CONFIG_PATH=/usr/local/ssl30/lib64/pkgconfig
Created at 1 day ago
pull request closed
Fix bug #74129: Incorrect SCRIPT_NAME with apache ProxyPassMatch when spaces are in path

As described in the pull request, this is caused by the fact that Apache URL decodes path info in the SCRIPT_NAME because it is required in CGI RFC.

Created at 3 days ago

Fix bug #74129: Incorrect SCRIPT_NAME with apache ProxyPassMatch

This happens when there are spaces are in the path info. The reason is that Apache decodes the path info part in the SCRIPT_NAME as per CGI RFC. FPM tries to strip path info from the SCRIPT_NAME but the comparison is done against SCRIPT_FILENAME which is not decoded. For that to work we have to decode it before comparison if there is any encoded character.

Closes GH-10869

Merge branch 'PHP-8.1' into PHP-8.2

Merge branch 'PHP-8.2'

Created at 3 days ago

Fix bug #74129: Incorrect SCRIPT_NAME with apache ProxyPassMatch

This happens when there are spaces are in the path info. The reason is that Apache decodes the path info part in the SCRIPT_NAME as per CGI RFC. FPM tries to strip path info from the SCRIPT_NAME but the comparison is done against SCRIPT_FILENAME which is not decoded. For that to work we have to decode it before comparison if there is any encoded character.

Closes GH-10869

Merge branch 'PHP-8.1' into PHP-8.2

Created at 3 days ago

Fix bug #74129: Incorrect SCRIPT_NAME with apache ProxyPassMatch

This happens when there are spaces are in the path info. The reason is that Apache decodes the path info part in the SCRIPT_NAME as per CGI RFC. FPM tries to strip path info from the SCRIPT_NAME but the comparison is done against SCRIPT_FILENAME which is not decoded. For that to work we have to decode it before comparison if there is any encoded character.

Closes GH-10869

Created at 3 days ago

Fix bug #74129: Incorrect SCRIPT_NAME with apache ProxyPassMatch when spaces are in path

Created at 4 days ago