RE: Passing multiple IFS directories

Matt,

Simply using Alias as you indicated caused me to lose access to the
sub-folders.

What does work however is the positioning as you mentioned.  Now that I have
/documents first, I'm now getting a 403 Forbidden.  If I move it after the
WebPages, as you said, it matches on the first and doesn't proceed.

Now I have to figure out why I'm getting the 403.  QTMHHTTP has read
authority to the folder but not the items within the folder.  Items are
added to the folder via an FTP process from a particular user profile.  Is
there a way such that when an item is added to a folder (in this case via an
FTP PUT), that other users could also be granted authority automatically or
can the QTMHHTTP user profile be granted authority to also have authority
automatically to objects owned by the other profile? 

-----Original Message-----
From: web400-bounces@xxxxxxxxxxxx [mailto:web400-bounces@xxxxxxxxxxxx] On
Behalf Of Haas, Matt
Sent: Wednesday, December 22, 2004 9:15 AM
To: Web Enabling the AS400 / iSeries
Subject: RE: [WEB400] Passing multiple IFS directories

Mike,

You don't need the AliasMatch's. Alias is the better choice for what you're
trying to do (AliasMatch uses regular expressions which adds extra load to
your server and since you're allowing everything, it's just extra work with
no benefit). Here's an example that should work:

Alias /documents /DocImage
Alias / /WebPages

<Directory /WebPages/>
   Allow From all
</Directory>
<Directory /DocImage/>
   Allow From all
</Directory>

If you'll notice, the Alias for "documents" is first. This is because the
server stops searching Alias' after if finds the first one that satisfies
the request. When you had it the other way around, it was matching on /
first.

An alternative to having the second Alias and Directory would be to create a
symbolic link via the ADDLNK command from WebPages to DocImage. I think
you'll need to set an option (either server level or in the Directory) to
follow symbolic links. Take a look at the documentation at
http://httpd.apache.org (make sure you look at the version 2 docs) for more
information on doing this.

Matt
-----Original Message-----
From: Mike Skvarenina [mailto:mskvarenina@xxxxxxx]
Sent: Wednesday, December 22, 2004 8:45 AM
To: WEB400@xxxxxxxxxxxx
Subject: [WEB400] Passing multiple IFS directories


This one should be a no-brainer for someone out there.

 

I've got 2 folders in my IFS I'm trying to serve via my Apache
implementation.  The first is a folder called WebPages and it contains a
number of sub-folders which all seem to serve just fine.  For example I can
say this in my web page <Img src="/images/photos/3362.JPG"> and the image
file located in WebPages/images/photos is served.

 

Below are the 2 directives I have in my config file for this folder.

 

<Directory /WebPages/>

   Allow From all

</Directory>

 

AliasMatch ^/(.*) /WebPages/$1

 

 

 

 

Now I have a second IFS folder that I'm trying to serve.  On the IFS, it's
actually called DocImage.  Below is what I added to my config file for this
folder.

 

<Directory /DocImage/>

   Allow From all

</Directory>

 

AliasMatch ^/documents/(.*) /DocImage/$1

 

 

My problem is however I cannot seem to reference items in the DocImage
folder.  I'd like to be able to say http://1.2.3.4/documents/document1.pdf
but all I get is a 404 File not found

 

 

Any help would be appreciated.

_______________________________________________
This is the Web Enabling the AS400 / 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 AS400 / 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.