We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I've noticed some protocol checks for HTTP/1.1.
web.php && preg_grep('/HTTP\/\d\.\d 200/',$response['headers']) preg_grep('/HTTP\/1\.\d 3\d{2}/',$headers) && if (preg_match('/HTTP\/1\.\d 304/',
&& preg_grep('/HTTP\/\d\.\d 200/',$response['headers'])
preg_grep('/HTTP\/1\.\d 3\d{2}/',$headers) &&
if (preg_match('/HTTP\/1\.\d 304/',
ws.php if (preg_match('/^(\w+)\s(.+)\sHTTP\/1\.\d$/', 'HTTP/1.1 400 Bad Request'.$EOL.
if (preg_match('/^(\w+)\s(.+)\sHTTP\/1\.\d$/',
'HTTP/1.1 400 Bad Request'.$EOL.
Etc.
[Question] We already have HTTP/1.1, HTTP/2 and HTTP/3. Should this code be updated?
E.g. preg_grep('/HTTP\/\d\.\d 200/',$response['headers']) replace with preg_grep('/HTTP\/[\d\.]{1,3} 200/',$response['headers'])
preg_grep('/HTTP\/\d\.\d 200/',$response['headers'])
preg_grep('/HTTP\/[\d\.]{1,3} 200/',$response['headers'])
The text was updated successfully, but these errors were encountered:
update HTTP protocol checks, #bcosca/fatfree#1190
39380a1
No bad idea.. fixed in f3-factory/fatfree-core@39380a1
Sorry, something went wrong.
No branches or pull requests
I've noticed some protocol checks for HTTP/1.1.
web.php
&& preg_grep('/HTTP\/\d\.\d 200/',$response['headers'])
preg_grep('/HTTP\/1\.\d 3\d{2}/',$headers) &&
if (preg_match('/HTTP\/1\.\d 304/',
ws.php
if (preg_match('/^(\w+)\s(.+)\sHTTP\/1\.\d$/',
'HTTP/1.1 400 Bad Request'.$EOL.
Etc.
[Question] We already have HTTP/1.1, HTTP/2 and HTTP/3. Should this code be updated?
E.g.
preg_grep('/HTTP\/\d\.\d 200/',$response['headers'])
replace with
preg_grep('/HTTP\/[\d\.]{1,3} 200/',$response['headers'])
The text was updated successfully, but these errors were encountered: