[PROC HTTP] Truncated response on one very long row

[ChrisHemedinger]

In the future, if you're working with a remote SAS session and you need to take a closer look at any file using local tools, use the Copy Files task to download a file from SAS to your local PC.  There you can examine with fancier tools like Notepad++ or VS Code, which can "prettify" your structured files for easier reading.

[ChrisNZ]

@ChrisHemedinger 

Maybe an improvement for EG would be for it to suggest downloading the file if it's too large to handle, like it does when outputs or logs are too large, rather than truncate without warning.

[ChrisHemedinger]

@ChrisNZ Usually EG would prompt to open a very large file in an external tool, like Notepad++.  

But the implicit download of a text-based file could cause issues with transcoding/line-ending nuances.  The Copy Files task always does a binary transfer.

[ChrisNZ]

> The Copy Files task always does a binary transfer.

That's good to know.

 it was displayed as cut in the EG text editor, which led me to believe the response was not correctly written.

The issue here seems to be that no warning was given about the truncation of that file, hence causing unnecessary confusion.

[JosephHenry]

So I tried this with the latest EG 7.1, and the limitation of 32768 characters on a single line is still there.

I will let the EG guys know, and maybe they can handle it better in the future.

[Andres_SAS]

Hi 

I was having the same problem, still can't solve it. What I could do to see the whole response is to change the extention of the file for html. 

So in your case it would be 

filename RESPONSE "&g_USER_BASE.\...\response_FULL.html";

Now I'm trying to extract the text from the html file into a several lines in a sas table for example

[Andres_SAS]

ok, and for that it does work the infile RESPONSE recfm=n