You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description
I'm encountering an issue with Guzzle where it appears to be attempting to make an HTTP request using the offsetGet method, which is not a standard HTTP method. This results in a 501 Not Implemented response from the server. The issue occurs intermittently on specific ECS instances, and all instances are running the same source code.
How to reproduce
The issue is intermittent and doesn't occur consistently, but here's a rough outline of how it can be observed:
Set up an environment with multiple ECS instances running the same source code and Guzzle configuration.
Occasionally, on one of the ECS instances, when making an HTTP request using Guzzle, the request may be incorrectly using the offsetGet method instead of a valid HTTP method.
This incorrect request results in a 501 Not Implemented response from the server is trigger from this code
Possible Solution
I don't have a specific solution at this time, as the issue is intermittent and doesn't seem to be directly related to the source code or Guzzle configuration. It may require further investigation to identify the root cause.
Additional context
The issue occurs on specific ECS instances, and all instances are running the same source code and configuration.
The issue does not consistently occur and seems to be related to a specific environment or configuration.
The GuzzleHttp\Client->__call('offsetGet', Array) error message suggests that there might be an unexpected dynamic method call or configuration issue within Guzzle.
Log bellow:
The GuzzleHttp\Client->__call('offsetGet', Array) error message suggests that there might be an unexpected dynamic method call or configuration issue within Guzzle.
I see this line GuzzleHttp\Client->__call('offsetGet', Array) is call when create new Client(), but offsetGet is weird parameter, I don't think it send from my code
Feel free to ask me to provide more code or information . Thank you !
This issue has been automatically marked as stale because it has not had recent activity. It will be closed after 2 weeks if no further activity occurs. Thank you for your contributions.
Guzzle version(s) affected: 6.3.3
PHP version: 7.2.34
cURL version: 7.74.0
Description
I'm encountering an issue with Guzzle where it appears to be attempting to make an HTTP request using the offsetGet method, which is not a standard HTTP method. This results in a 501 Not Implemented response from the server. The issue occurs intermittently on specific ECS instances, and all instances are running the same source code.
How to reproduce
The issue is intermittent and doesn't occur consistently, but here's a rough outline of how it can be observed:
Set up an environment with multiple ECS instances running the same source code and Guzzle configuration.
Occasionally, on one of the ECS instances, when making an HTTP request using Guzzle, the request may be incorrectly using the offsetGet method instead of a valid HTTP method.
This incorrect request results in a 501 Not Implemented response from the server is trigger from this code
Possible Solution
I don't have a specific solution at this time, as the issue is intermittent and doesn't seem to be directly related to the source code or Guzzle configuration. It may require further investigation to identify the root cause.
Additional context
Log bellow:
I have done some research on the internet and found a link related to the topic.
https://stackoverflow.com/questions/66710501/guzzlehttp-sending-weird-request-with-weird-http-method
The temporary solution is to reset the container, in accordance with the current situation. But it will continue in the future.
The text was updated successfully, but these errors were encountered: