Re: R: Re: external CSS style sheets problem

He isn't specifying a "/" in the html. The href is simply "mobile.css" and if that fails then either its isn't in the same location as the html file or QTMHHTP1 is not authorised to the file.

If "mobile.css" is truly in the document root, then href="/mobile.css" (with a forward slash) would work regardless of where the html file lived.

The original question suggests that the css is not in the document root anyway, unless it has been relocated since.


[https://www.netcracker.com/assets/img/netcracker-social-final.png] ƕ
-----Original Message-----
From: WEB400 [mailto:web400-bounces@xxxxxxxxxxxx] On Behalf Of Steve Richter
Sent: 30 January 2017 12:40
To: Web Enabling the IBM i (AS/400 and iSeries) <web400@xxxxxxxxxxxx>
Subject: Re: [WEB400] R: Re: external CSS style sheets problem

just try it without the forward slash. in the chrome browser, use F12
developer tools to see if the CSS file is being loaded or not.


On Mon, Jan 30, 2017 at 7:12 AM, gio.cot <gio.cot@xxxxxxxxxxx> wrote:

Hi Kevin

thanks for your patience



but my "mobile.css" is already in : "/www/articles/htdocs" .. is
this why I don't understand why not works



or have not I understood anything?

Thanks





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




________________________________
The information transmitted herein is intended only for the person or entity to which it is addressed and may contain confidential, proprietary and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from any computer.