{"version":"2.1.290","anchor":"remote-session-errors-now-redact-response-bodies-and-url-pro","canonical_anchor":"remote-session-errors-now-redact-response-bodies-and-url-pro","heading":"Remote-session errors no longer quote raw server responses","tier":"notice","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290\/e\/remote-session-errors-now-redact-response-bodies-and-url-pro","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290","markdown":"### Remote-session errors no longer quote raw server responses\n\nTwo remote-session error messages now leave out raw server responses and URL details when they are not safe to quote\n\n**What**\n\nTwo error messages used with remote sessions no longer print raw values:\n\n- The error for an invalid worker epoch in a server response now quotes the response only when it is safe. Otherwise it says \"(the response is not quoted: it is too long or is not one plain line)\".\n\n- The error for a URL that is not http or https now leaves out the protocol it received when that is not safe to quote.\n\n**Why**\n\nError text is now cleaned up, so less raw data ends up in logs.\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}