Closed udivankin closed 10 months ago
The same happened to me; it began after I updated my browser's extension to 0.28. Both the Firefox and Chrome browsers were checked. Both are affected.
@udivankin Is the selfhosted version being used by you?
@AndrewBastin can you check this?
Yes, I can reproduce this, for the time being, a fix for it is to set the Body Content-Type to None on your requests having GET/HEAD to prevent the app from sending a body to the extension.
I will push a patch to the extension to ignore the body field on GET/HEAD methods.
Thank you, @AndrewBastin It's working now.
This error message appears when we attempt to click the send button repeatedly. Upon restarting the browser, everything functions as intended.
@sats268842 can you open this as a new issue on this repo ?
cc: @amk-dev
I have issued a new release 0.29 which will ignore the body on GET/HEAD
method calls. It should be available on both the browsers in a couple of hours.
Is there an existing issue for this?
Current behavior
GET/HEAD requests stopped working after a recent Chrome update.
Steps to reproduce
Export to curl/fetch shows the body param (which is empty) - may be the cause.
Environment
Production
Version
Local