Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
Message from discussion Securing uploaded documents
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Dan  
View profile  
 More options Jun 2 2010, 8:49 am
Newsgroups: microsoft.public.inetserver.asp.general
From: "Dan" <n...@worldofspack.com>
Date: Wed, 2 Jun 2010 13:49:12 +0100
Local: Wed, Jun 2 2010 8:49 am
Subject: Re: Securing uploaded documents

"Bwig Zomberi" <zomberiMAPSONNOS...@gmail.com> wrote in message

news:hu5ein$4qs$1@speranza.aioe.org...

> Dean g wrote:
>> Damn, 2 out of 3 problems solved is still good.

>> Thanks for the help guys, i just wish i knew why half the pdf
>> files display garbage on the screen even though they are
>> genuine pdf's. i guess thats a question for another group
>> though.

> I had this problem with Opera. In a newer version, it got solved.

> Just ensure that you set the content type properly on the server-side and
> you are not writing anything other than what is in the PDF to the browser.
> To be sure that the entire ASP code is between one set of <% and %>. Do
> not use nested code. Do not write any HTML or set any cookies.

> On the client side, ensure that Adobe Reader is installed properly and
> plugins are available for all browsers.

> If the problems persist, then it is problem with the PDFs. You could go to
> alt.txt.pdf. However, you will need to host the PDF and provide a link so
> they can check it out.

The other thing you can do is use Response.Buffer = true, and then prior to
sending the headers clear the buffer first just in case there are any CR/LF
characters from inline ASP above that piece of code. Or just make sure you
always put inline ASP code fully inline, eg.

<%
blah blah
%>
<%
more blah
write headers
write binary data
%>

will actually put a single CR/LF combination before the data, because there
is a CRLF outside of the ASP tags. The same can be written as

<%
blah blah
%><%
more blah
write headers
write binary data
%>

and not insert the CR/LF.

It's also worth checking this wherever you send out a DOCTYPE headers in
normal HTML, if the DOCTYPE isn't on the first line of the output then some
browsers will ignore it.

--
Dan


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.