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
{{ message }}
Repository navigation
[Bug]: REST /tasks/{id}:subscribe uses GET method instead of POST #840
Applies to both 0.3 version from main and 1.0 RC from 1.0-dev, to both client and server.
BUT fixing it for 0.3 is a bit dangerous as one may had assumptions around wrong implementation, so the proposal is:
For 1.0 server and client it should just be fixed.
1.0 client in compat 0.3 mode should use POST method as per the spec to be compatible with other SDKs which implement it properly. We may have a flag in the legacy compat transport to use GET if one needs to talk to old Python server which uses wrong method.
0.3 server should accept both to work with old clients.
changed the title [-][Bug]: GET method is used for `/v1/tasks/{id}:subscribe`[/-][+][Bug]: GET method is used for REST `/tasks/{id}:subscribe` [/+]on Mar 16, 2026
changed the title [-][Bug]: GET method is used for REST `/tasks/{id}:subscribe` [/-][+][Bug]: REST `/tasks/{id}:subscribe` uses GET method instead of POST[/+]on Mar 16, 2026
Activity
[-][Bug]: GET method is used for `/v1/tasks/{id}:subscribe`[/-][+][Bug]: GET method is used for REST `/tasks/{id}:subscribe` [/+][-][Bug]: GET method is used for REST `/tasks/{id}:subscribe` [/-][+][Bug]: REST `/tasks/{id}:subscribe` uses GET method instead of POST[/+]fix: Use POST method for REST endpoint /tasks/{id}:subscribe (#843)