Simon Sprankel

Could this please be merged? @sidolov @sinhaparul

I think this is a valid feature request and a common request. I think we should have a new config field similar to this: https://github.com/firegento/firegento-magesetup2/blob/a0f36405e236d2238e40e812234bd38244f9a31e/etc/adminhtml/system.xml#L138-L143 Then we can check this...

Any update on this? 🙈 Thanks!

Thanks, @sreichel! I see that the [PR](https://github.com/netz98/n98-magerun/pull/1484) has merge conflicts, though. Could you resolve them? And afterwards, I guess it is up to @cmuench to review / merge / release...

If you have doubts regarding the parameters, check https://github.com/mpchadwick/tracking-query-params-registry/blob/master/_data/params.csv, where all of them are mentioned including a reference.

Thanks for the feedback, @hostep. I guess it would be easiest if I include the parameter here in this PR. Or should I try to cherry-pick that other commit to...

I now cherry-picked the changes from https://github.com/magento/magento2/pull/35228 and also applied the change to the Varnish 7 VCL.

In my case, this is https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issues/#api-rest-api-3-issue-issueidorkey-assignee-put. As you can see, it returns HTTP status code 204 No Content. I don't think there should be an error if the response is...

I wouldn't care too much if there was an error like "The response is empty. If this is expected, use the "Always Output Data" option in the settings". However, this...

@Joffcom, I tested this in a test workflow myself using https://httpstat.us/204. Unfortunately, I also cannot reproduce the issue then. I compared my failing node and the working node in my...