I think *RX is only needed for CGI type directories. HTML, images, etc. files only need *R.

Thank you,
Schadd Gray
Damon Technologies, Inc.
www.damontech.com
-----Original Message----- From: Bradley Stone
Sent: Tuesday, February 26, 2013 8:18 AM
To: Web Enabling the IBM i (AS/400 and iSeries)
Subject: Re: [WEB400] Link to a PDF on IFS

QTMHHTP1 as well if it's CGI. And I recall needing to give directories *RX
authority, just *R didn't work.

That may have changed.. I haven't played around with authorities since I
got them working.. :)

Brad
www.bvstools.com


On Tue, Feb 26, 2013 at 8:16 AM, Vernon Hamberg <vhamberg@xxxxxxxxxxxxxxx>wrote:

LOL - Oh, good! ;)

On 2/26/2013 6:29 AM, Schadd Gray wrote:
> Vern,
>
> You are correct.
>
> Thank you,
> Schadd Gray
> Damon Technologies, Inc.
> www.damontech.com
> -----Original Message-----
> From: Vernon Hamberg
> Sent: Monday, February 25, 2013 9:58 PM
> To: Web Enabling the IBM i (AS/400 and iSeries)
> Subject: Re: [WEB400] Link to a PDF on IFS
>
> Schadd
>
> Do you really need to give *R to *PUBLIC? Shouldn't it be enough to give
> it to the user of the Apache server, which would be QTMHHTTP, probably?
>
> Vern
>
> On 2/25/2013 8:05 PM, Schadd Gray wrote:
>> Yes, you could use Alias to map outside of the htdocs sandbox, however
>> that
>> just opens you up to potential security issues. You would need to >> grant
>> *R
>> authority to *Public on those folders. If you are going to do that you
>> should just put them under the htdocs structure and let the inheritance
>> handle authorization. What would be the purpose of opening up other
parts
>> of your IFS? This method also makes it so that anyone can access those
>> PDF
>> files. The second method easily allows for restricting the user that
can
>> access the file, you only hand them the ones they should see.
>>
>> Thank you,
>> Schadd Gray
>> Damon Technologies, Inc.
>> www.damontech.com
>> -----Original Message-----
>> From: franz400
>> Sent: Monday, February 25, 2013 5:32 PM
>> To: Web Enabling the IBM i (AS/400 and iSeries)
>> Subject: Re: [WEB400] Link to a PDF on IFS
>>
>> I'd like to disagree with the "outside of htdocs...you cannot expose it
to
>> the web" statement.
>> It just takes a directive in the Apache config, and it can be a naming
>> that
>> is hidden from the url
>> so you are not exposing your true dir structure. Then it's a matter of
the
>> url pointing to
>> the .pdf instead of a .html and your browser will know what to do. Have
>> been
>> serving .pdf
>> (or .csv or .xls) this way to the web since 2000 in a similar tool -
>> Websmart.
>> Jim Franz
>>
>> ----- Original Message -----
>> From: "Schadd Gray" <list@xxxxxxxxxxxxx>
>> To: "Web Enabling the IBM i (AS/400 and iSeries)" <web400@xxxxxxxxxxxx>
>> Sent: Monday, February 25, 2013 8:40 AM
>> Subject: Re: [WEB400] Link to a PDF on IFS
>>
>>
>>> I do not know much about LANSA, but in other web languages, if the PDF
>>> file
>>> on the IFS is outside of the web directory (/www/mysite/htdocs) you
>>> cannot
>>> expose it to the web. You have two choices. 1) Place the PDF in the
web
>>> directory, but this allows every web user to access this PDF if they
know
>>> the path (not very secure). 2) Write a program to read the file from
the
>>> IFS and pipe it to the browser. You would need to change the content
>>> type
>>> to "application/pdf".
>>>
>>> Thank you,
>>> Schadd Gray
>>> Damon Technologies, Inc.
>>> www.damontech.com
>>> -----Original Message-----
>>> From: Jack Tucky
>>> Sent: Sunday, February 24, 2013 7:37 PM
>>> To: web400@xxxxxxxxxxxx
>>> Subject: [WEB400] Link to a PDF on IFS
>>>
>>> I'm using LANSA on Iseries to run a website. The user can press a
>>> button,
>>> I
>>> call a CLP and create a PDF and email it to the end user.
>>>
>>>
>>>
>>> I'd like to change it to display the PDF in the browser. The PDF is >>> on
>>> the
>>> IFS. I know the path and file name of the PDF.
>>>
>>>
>>>
>>> What do I have to do to change the webserver show files from a >>> specific
>>> directory on the IFS?
>>>
>>>
>>>
>>> Thanks, Jack.
>>>
>>>
>>>
>>>
>>>
>>> --
>>> This is the Web Enabling the IBM i (AS/400 and iSeries) (WEB400)
mailing
>>> list
>>> To post a message email: WEB400@xxxxxxxxxxxx
>>> To subscribe, unsubscribe, or change list options,
>>> visit: http://lists.midrange.com/mailman/listinfo/web400
>>> or email: WEB400-request@xxxxxxxxxxxx
>>> Before posting, please take a moment to review the archives
>>> at http://archive.midrange.com/web400.
>>>
>>> --
>>> This is the Web Enabling the IBM i (AS/400 and iSeries) (WEB400)
mailing
>>> list
>>> To post a message email: WEB400@xxxxxxxxxxxx
>>> To subscribe, unsubscribe, or change list options,
>>> visit: http://lists.midrange.com/mailman/listinfo/web400
>>> or email: WEB400-request@xxxxxxxxxxxx
>>> Before posting, please take a moment to review the archives
>>> at http://archive.midrange.com/web400.
>>>

--
This is the Web Enabling the IBM i (AS/400 and iSeries) (WEB400) mailing
list
To post a message email: WEB400@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/web400.



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2022 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.