Re: Opening PDF in browser fails when web server protects files via "referer"

Article View: adobe.reader

Article #2766

#2766

From: George Johnson
Date: Mon, 08 Dec 2008 21:13

3 lines
1018 bytes

FWIW, that's not really security as the headers can easily be manipulated. You might want to check the server logs to see what the referrer is, and you could then add whatever it is to the server configuration. But check different versions of Acrobat/Reader to make sure it's consistent. Also, consider what should happen if the user has a non-Adobe PDF viewer.

George

Technical Details

Message-ID: <59b73743.0@webcrossing.la2eafNXanI>

Path: arc1-ca.pugleaf.net!g2news1.google.com!news1.google.com!news.glorb.com!news2!newshub.sdsu.edu!webcrossing

References: <59b73743.-1@webcrossing.la2eafNXanI>

Show Full Headers

Complete Article Headers

X-Google-Thread: 10273d,3a0e3fc3a7dfb2d3
X-Google-Attributes: gid10273d,domainid0,public,usenet
X-Google-Language: ENGLISH,ASCII-7-bit
From: "George Johnson" <acroscript@gmail.com>
Path: arc1-ca.pugleaf.net!g2news1.google.com!news1.google.com!news.glorb.com!news2!newshub.sdsu.edu!webcrossing
Newsgroups: adobe.reader
Subject: Re: Opening PDF in browser fails when web
 server protects files via "referer"
Message-ID: <59b73743.0@webcrossing.la2eafNXanI>
Date: Mon, 8 Dec 2008 13:13:22 -0800
References: <59b73743.-1@webcrossing.la2eafNXanI>
Lines: 8
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit

Reply to Parent Message