On Fri, Jul 31, 2009 at 9:19 AM, David Smith wrote:
> One way to handle the paths in jsps is to use something like
> ${pageContext.request.contextPath}/webapp_relative_path/to_my_resource.css.
OTOH, if you use the standard taglib to wrap all your urls, e.g.
foo
they'll be both context-aware
Roman Sokolyuk wrote:
> Thank you very much for your time.
> This fixed the problem.
>
> I have only one question. How does the browser determine which parts of the
> URL to strip?
>
> On Fri, Jul 31, 2009 at 11:07 AM, André Warnier wrote:
>
>
One way to handle the paths in jsps is to use some
André Warnier wrote:
> As an addendum :
>
> A very useful tool when dealing with issues like this one, if your are
> using Firefox as a browser, is an add-on like "HttpFox".
> It allows you to access your server, and see exactly which requests
> are sent to the server (including the "secondary" one
Roman Sokolyuk wrote:
> Additionally, does it follow that elements have to refer to images
> located outside the WEB-INF directory (Since no content from WEB-INF can be
> served directly to the browser request)?
Simple answer: Yes.
More complicated: There are ways around this limitation using a
Roman Sokolyuk wrote:
Additionally, does it follow that elements have to refer to images
located outside the WEB-INF directory (Since no content from WEB-INF can be
served directly to the browser request)? Is there a way to use CSS and
images from within WEB-INf so that a client wouldn't be able
On Fri, Jul 31, 2009 at 8:17 AM, Roman Sokolyuk wrote:
> Additionally, does it follow that elements have to refer to images
> located outside the WEB-INF directory (Since no content from WEB-INF can be
> served directly to the browser request)?
Yes.
Is there a way to use CSS and
> images from w
Roman Sokolyuk wrote:
Thank you very much for your time.
This fixed the problem.
I have only one question. How does the browser determine which parts of the
URL to strip?
It has very precise rules for that, which are probably to be found in
the HTTP RFC (http://www.faqs.org/rfcs/rfc2616.html),
2009/7/31 Roman Sokolyuk :
> I have only one question. How does the browser determine which parts of the
> URL to strip?
>
http://tools.ietf.org/html/rfc3986#section-5
http://www.w3.org/TR/html401/struct/links.html#h-12.4.1
Also, if I remember correctly, unless you remove this line:
it won't wo
Additionally, does it follow that elements have to refer to images
located outside the WEB-INF directory (Since no content from WEB-INF can be
served directly to the browser request)? Is there a way to use CSS and
images from within WEB-INf so that a client wouldn't be able to get to them
on its o
As an addendum :
A very useful tool when dealing with issues like this one, if your are
using Firefox as a browser, is an add-on like "HttpFox".
It allows you to access your server, and see exactly which requests are
sent to the server (including the "secondary" ones like your stylesheet
and j
Thank you very much for your time.
This fixed the problem.
I have only one question. How does the browser determine which parts of the
URL to strip?
On Fri, Jul 31, 2009 at 11:07 AM, André Warnier wrote:
> Roman Sokolyuk wrote:
> ...
>
>
>> header2.jsp
>> --
>>> type="te
Roman Sokolyuk wrote:
...
header2.jsp
--
...
The CSS directory is under the app context, alongside WEB-INF.
Am I specifying the path to the CSS correctly? Anyone can suggest what else
I may be doing wrong?
I am not a JSP specialist, but I would guess that your pr
Hi,
I built a few XHTML pages for a personal website and added style with CSS.
In a browser everything looks great. I converted the pages into JSP's and
the style no longer registers.
Here is the JSP markup:
home.jsp
<%@ include file="header1.jsp" %>
My Site: Home
<%@
13 matches
Mail list logo
