Browser instrumentation injection results in invalid Content-Length headers with latest rack versions about newrelic-ruby-agent

[tannalynn]

Just letting you know we released the new version 6.9.0 that includes the fix for this! Thanks everyone!

[Paul-Yves]

Hi. I just experienced the same, and downgraded to rack 2.0.9 (which support samesite option on cookies)

[rachelleahklein]

Hi @tanelsuurhans. Thanks for reaching out to us about this!

We have actually already received a pull request fixing this, which we have accepted and plan to include in our next agent release.

[lmansur]

Hi @rachelleahklein

I was just wondering if there's any news on when #312 will be released. My Sidekiq UI is not working due to this issue. Thanks!

[rachelleahklein]

Hi, @lmansur. I don't have a specific date to give you for our next release, but we're actively working on it. We will update this issue when the fix is released so you'll know right away.

[lmansur]

Thanks @rachelleahklein 👍

[bbay]

Hey @tanelsuurhans I somehow pinned down the problem to NewRelic as well but I was going completely crazy for days. Thank you so much for your investigation 👍

Downgrading rack to 2.0.8 did the trick for me.

[dentarg]

Setting NEW_RELIC_BROWSER_MONITORING_AUTO_INSTRUMENT=false seems to be a workaround for this (if you don't want to downgrade rack)