Hi,

I have an IBM HTTP server running on an IBMi. The server directories in the IFS are located at: /www/MYWEBSERVER/.

I am getting 403 Forbidden errors for any resources that I place in subfolders of htdocs. For example, I get 403 Forbidden errors for:

* /www/MYWEBSERVER/htdocs/css/style.css
* /www/MYWEBSERVER/htdocs/img/myphoto.png
* /www/MYWEBSERVER/htdocs/anotherapp/index.html

Is this an IFS directory permissions problem?

I tried Googling for answers. I also looked at the 644 page pdf documentation on IBM HTTP Server for i, which mentions 403 Forbidden errors only three times, and then only in the context of the directive AuthzSendForbiddenOnFailure. I am new to web server administration. But I don't think I should be using this directive to solve the problem that I'm having.

Below is more detail using the style.css file as an example.

I uploaded an index.html file and a style.css file into the /www/MYWEBSERVER/htdocs/ directory. I used a browser to navigate to the URL. I saw my web page with the CSS applied.

I then created a new /www/MYWEBSERVER/htdocs/css/ directory. I moved my style.css style sheet into the new directory. I changed the link tag in the head of my index.html file to read:

href="css/style.css"

instead of:

href="style.css"

Now, when I navigate to the URL, I see my web page, but none of the CSS is applied. When I opened the developer tools in Chrome, I see a message that says:

GET http://MYSYSTEM:MYPORT/css/style.css net::ERR_ABORTED 403 (Forbidden)

Thanks,

Kelly Cookson
Senior Software Engineer II
Dot Foods, Inc.
217-773-4486 ext. 12676
www.dotfoods.com<http://www.dotfoods.com/>


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

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

This mailing list archive is Copyright 1997-2024 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.