
The reason that I'm reluctant to add a file extension to the Url is that the suggested download name is generated from item data, submitted with the response and otherwise totally unrelated to the ID. Note, how the second request reduces the 'Accept:' header to just */*.

User-Agent: Mozilla/5.0 (compatible MSIE 9.0 Windows NT 6.1 WOW64 Trident/5.0)Ĭookie: ASP.NET_SessionId=52znkt1fcisrolj44tnuyzu4 The requests differ, however (samples slightly edited):Īccept: text/html, application/xhtml+xml, */* The issue is clearly data-dependent, meaning that some generated files download fine on the first attempt while others reproducibly need the retry.įiddler shows the server responses to be identical on each access, as far as I can tell.

Our application is creating PDF documents on the fly and offering them as downloads. But looking at the situation with fiddler & co., I have some more information that may be of help. I have the same problem and cannot offer a good solution (besides what Tood suggests, which is an option). The grep command is primarily used to search text or any file for lines that contain a match to the specified words/strings.
