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
Describe the bug
n8n's axios library appears to send invalid GET requests with an HTTP body. While most services accept this, intermediate proxies often reject them. I have confirmed this occurs with both Github and Clockify nodes.
To Reproduce
Steps to reproduce the behavior:
Configure http_proxy and https_proxy environment variables to use an http proxy
Add a Github or Clockify node, potentially others
Configure a resource and operation that makes a GET request
Github: Resource: User, Operation: Get Repositories
Clockify: Resource: Workspace, Operation: Get all
Send the request
See error
Packet capture showing empty body with GET request:
Squid proxy error:
Expected behavior
GET requests should not have request bodies. Although not strictly prohibited by the spec, a GET body has no semantic meaning. Similar to Python requests library a GET request with a body should be considered invalid.
Describe the bug
n8n's axios library appears to send invalid GET requests with an HTTP body. While most services accept this, intermediate proxies often reject them. I have confirmed this occurs with both Github and Clockify nodes.
To Reproduce
Steps to reproduce the behavior:
Packet capture showing empty body with GET request:
Squid proxy error:
Expected behavior
GET requests should not have request bodies. Although not strictly prohibited by the spec, a GET body has no semantic meaning. Similar to Python
requests
library a GET request with a body should be considered invalid.Environment (please complete the following information):
Additional context
None
The text was updated successfully, but these errors were encountered: