Cool scenario.
Yes, unfortunately the .NET Framework inherently limits all objects to a 2GB size, and as a consequence earlier versions of the AutoResponder could not return responses over 2gb. Update: Fiddler version 2.4.9.4 and later automatically detect huge files; any X-ReplyWithFile
body over 262 megabytes (fiddler.memory.DropIfOver
preference) will be streamed from the client and not stored in memory.
You could use Fiddler to return a HTTP/307
redirect to a different webserver and host the huge file there.
Your event handler could also directly stream the bytes of the file to the client in chunks (without using the x-replywithfile feature) using the oSession.oRequest.pipeClient.Send
method, but this would involve a significant amount of code.