Bad content-length header

[SeanHayes]

I have a scope that was recorded with nock.bak that looks like this:

{
    "scope": "https://api.example.com:443",
    "method": "GET",
    "path": "/mypath?platform=web&key=JJHDC7UK73EH",
    "body": "",
    "status": 200,
    "response": {
        "anonid": "Mjk2MjEyMDc5"
    },
    "rawHeaders": [
        "Access-Control-Allow-Origin",
        "*",
        "Content-Type",
        "application/json",
        "Date",
        "Wed, 07 Mar 2018 09:50:09 GMT",
        "Server",
        "nginx/1.12.2",
        "Set-Cookie",
        "scookie=; path=/; expires=Thu, 01-Jan-1970 00:00:00 GMT",
        "X-Redux-Status",
        "ZOOL",
        "Content-Length",
        "30",
        "Connection",
        "Close"
    ]
},

That response may have originally been 30 bytes long, but I suspect that since it's stored as an inline data structure, nock will serialize it without the original pretty printing.

Is there a way to force nock to always store the original request?

[gr2m]

Hmm could you please create a PR with a failing pull request? That will help us investigate the issue

[SeanHayes]

I added PR #1095

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. We try to do our best, but nock is maintained by volunteers and there is only so much we can do at a time. Thank you for your contributions.

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue and add a reference to this one if it’s related. Thank you!