Hi



I try to clarify all



1) In my first post I said that the folder structure in IFS was :

www

..articles

...CSS

.....mobile.css

...htdocs

.....mobileorder.html

And that in my html, I had : <link rel="stylesheet" type="text/css"
href="/articles/CSS/mobile.css">



2) Then after Booth Martin suggestion i moved mobile.css in htdocs and
modified html to <link rel="stylesheet" type="text/css" href="mobile.css">

3) After the point 2, I said that:

"After your suggestion, now in preview it works, but when I run it in the
browser in see this error :
" <http://192.168.xx.z:Myport/cgi-bin/mobile.css>
http://192.168.xx.z:Myport/cgi-bin/mobile.css HTTP/1.1 404 Not Found 5ms "



Note "/cgi-bin/mobile.css" , it seems that when look for mobile.css, it
use the "ScriptAlias /cgi-bin/ /QSYS.LIB/ARTICLES.LIB/" HTTP directive and
pheraps it search in /QSYS.LIB/ARTICLES.LIB ?



So, NOW I have this scenario



folder structure in IFS:

www

..articles

...CSS

...htdocs

.....mobile.css

.....mobileorder.html



And in the HTML <link rel="stylesheet" type="text/css" href="mobile.css">



My DocumentRoot is /www/articles/htdocs



These the Apache directive

<Directory />

Order Deny,Allow

Deny From all

</Directory>

<Directory /QSYS.LIB/ARTICLES.LIB>

Order Allow,Deny

Allow From all

</Directory>

<Directory /www/articles/htdocs>

Order Allow,Deny

Allow From all

</Directory>

ScriptAlias /cgi-bin/ /QSYS.LIB/ARTICLES.LIB/

Alias /articles/ /articles/



And if I use Firefox developer tool , in the console I see

GET http://192.168.50.6:8017/cgi-bin/mobile.css [HTTP/1.1 404 Not
Found 10ms]



Sorry for the confusion, now I hope is clearer

Thanks all




















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-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.