The server committed a protocol violation. Section=ResponseStatusLine

[Alon Albert]

I have an ASP.NET that has an aspx that serves a binary file for download. I
need this rather than a direct link for various reasons.

I am getting the following error intermitently:

The server committed a protocol violation. Section=ResponseStatusLine

I tried adding:
<system.net>
<settings>
<httpWebRequest useUnsafeHeaderParsing="true" />
</settings>
</system.netto the web.config file but made no difference.

I am using .NET 2.0.
The download client is also a .NET application.

The code that serves the file looks like this:

private void Page_Load(object sender, System.EventArgs e) {
string filename = Request["filename"];
string path = string.Format("c:/files/{0}", filename);

Response.ContentType = "APPLICATION/octet-stream";
Response.AddHeader("Content-Disposition",
string.Format("attachment;filename={0}", filename));
FileInfo fi = new FileInfo(path);
Response.AddHeader("Content-Length", fi.Length.ToString());
Response.Flush();
Response.TransmitFile(path);
Response.End();
}

The client code reads from
WebRequest.Create(url).GetResponse().GetResponseSt ream().

Any ideas? I have run out of my own.

[=?Utf-8?B?UGV0ZXIgQnJvbWJlcmcgW0MjIE1WUF0=?=]

I think the problem may be the "attachment;" header. If you are using
WebRequest, what you really want to do is just stream out the data, not as an
"attachment".
Peter

--
Site: http://www.eggheadcafe.com
UnBlog: http://petesbloggerama.blogspot.com
Short urls & more: http://ittyurl.net


"Alon Albert" wrote:

I have an ASP.NET that has an aspx that serves a binary file for download. I
need this rather than a direct link for various reasons.

I am getting the following error intermitently:

The server committed a protocol violation. Section=ResponseStatusLine

I tried adding:
<system.net>
<settings>
<httpWebRequest useUnsafeHeaderParsing="true" />
</settings>
</system.netto the web.config file but made no difference.

I am using .NET 2.0.
The download client is also a .NET application.

The code that serves the file looks like this:

private void Page_Load(object sender, System.EventArgs e) {
string filename = Request["filename"];
string path = string.Format("c:/files/{0}", filename);

Response.ContentType = "APPLICATION/octet-stream";
Response.AddHeader("Content-Disposition",
string.Format("attachment;filename={0}", filename));
FileInfo fi = new FileInfo(path);
Response.AddHeader("Content-Length", fi.Length.ToString());
Response.Flush();
Response.TransmitFile(path);
Response.End();
}

The client code reads from
WebRequest.Create(url).GetResponse().GetResponseSt ream().

Any ideas? I have run out of my own.

[Alon Albert]

I'll give it a try. I think the reason I put that in was so that if I
download from a browser, it will prompt the proper filename rather than the
aspx page name. I think I found this in a an example somewhere. Is there
another way to do this? have the filename be prompted properly I mean?

Also, any idea why this would be happening intermittently?

"Peter Bromberg [C# MVP]" <pb*******@yahoo.yabbadabbadoo.comwrote in
message news:64**********************************@microsof t.com...

>I think the problem may be the "attachment;" header. If you are using
WebRequest, what you really want to do is just stream out the data, not as
an
"attachment".
Peter

--
Site: http://www.eggheadcafe.com
UnBlog: http://petesbloggerama.blogspot.com
Short urls & more: http://ittyurl.net


"Alon Albert" wrote:

>I have an ASP.NET that has an aspx that serves a binary file for
download. I
need this rather than a direct link for various reasons.

I am getting the following error intermitently:

The server committed a protocol violation. Section=ResponseStatusLine

I tried adding:
<system.net>
<settings>
<httpWebRequest useUnsafeHeaderParsing="true" />
</settings>
</system.netto the web.config file but made no difference.

I am using .NET 2.0.
The download client is also a .NET application.

The code that serves the file looks like this:

private void Page_Load(object sender, System.EventArgs e) {
string filename = Request["filename"];
string path = string.Format("c:/files/{0}", filename);

Response.ContentType = "APPLICATION/octet-stream";
Response.AddHeader("Content-Disposition",
string.Format("attachment;filename={0}", filename));
FileInfo fi = new FileInfo(path);
Response.AddHeader("Content-Length", fi.Length.ToString());
Response.Flush();
Response.TransmitFile(path);
Response.End();
}

The client code reads from
WebRequest.Create(url).GetResponse().GetResponseS tream().

Any ideas? I have run out of my own.

[Alon Albert]

In article <64**********************************@microsoft.co m>,
pb*******@yahoo.yabbadabbadoo.com says...

I think the problem may be the "attachment;" header. If you are using
WebRequest, what you really want to do is just stream out the data, not as an
"attachment".

Well, I removed the attachment code but it still happens. Any other
ideas?