Thanks Chuk,
>> In some discussion i heard that the WEB-INF contents can not be
>> accessed from Internet at all.
>
> The servlet spec requires that the servlet container (Tomcat) prevent direct
> access to WEB-INF.
>
>> How far this is true ?
>
> Completely, as far as Tomcat is concerned. If yo
On 05/12/2009 12:08, André Warnier wrote:
Vadim Letitchevski wrote:
I am working under Linux actually.
Ok, then what kind of Linux ?
Also, tell us the version of Tomcat you are talking about, and whether
you installed it from the pre-packaged version offered by your Linux
version, or directly
> From: R. S. Patil [mailto:kpr.rspa...@gmail.com]
> Subject: Security Query.
>
> In some discussion i heard that the WEB-INF contents can not be
> accessed from Internet at all.
The servlet spec requires that the servlet container (Tomcat) prevent direct
access to WEB-INF.
> How far this is tr
Thanks for reply Mark,
So you suggest to change the following method:
protected String encodeToken(String username, String value)
{
StringBuilder sb = new StringBuilder();
sb.append(username);
sb.append(":");
sb.append(value);
return Base64.encodeBytes(sb.toString
Hello,
I am a total newbie to web applications and tomcat, a student.
In some discussion i heard that the WEB-INF contents can not be accessed
from Internet at all. So one can keep secret information in that
folder in plain text files
How far this is true ?
if not then where to put secret inform
Mark Thomas wrote:
itay sahar wrote:
Caused by: java.lang.IllegalArgumentException: Control character in cookie
value, consider BASE64 encoding your value
at
org.apache.tomcat.util.http.ServerCookie.maybeQuote2(ServerCookie.java:396)
To cause this, there must be a character in the valu
hi Ahmed,
JAR files are not "loaded" by Tomcat. A jar file is just a container of
classes, the classes are loaded by the JVM when the code makes reference to
them.
If you specify a on your context.xml, then Tomcat will look
for those classes (the driverClassName), but that does not mean th
itay sahar wrote:
> Caused by: java.lang.IllegalArgumentException: Control character in cookie
> value, consider BASE64 encoding your value
> at
> org.apache.tomcat.util.http.ServerCookie.maybeQuote2(ServerCookie.java:396)
To cause this, there must be a character in the value with an ASCII
On Fri, Dec 04, 2009 at 05:08:05PM -0500, Christopher Schultz wrote:
>
> [snip]
>
> > log4j.rootLogger=DEBUG, cons
>
> See Jeffrey's suggestion in his post.
OK. I changed that... and I'm working my way through the Log4J
docs to better understand how it works...
> > log4j.appender.myAppender.F
This is not my code. It is seam code.
see below the encoding section:
protected String encodeToken(String username, String value)
{
StringBuilder sb = new StringBuilder();
sb.append(username);
sb.append(":");
sb.append(value);
return Base64.encodeBytes(sb.toString()
Hi,
I have few jars which need to get loaded only when the war file is getting
loaded or when the request comes, to be more clear I have some jar which is
having connection to DB, if I specify in my context.xml file it is getting
loaded when the server getting started up initially, so I want to
itay sahar wrote:
Hi all,
I'm using seam on tomcat 6.0.20 and encounter problem in my security module.
Basically, i try to add cookie with base64 encoding of the username which is
email address.
The encoding works and no exception is thrown. But when seam try adding the
cookie an exception i
Vadim Letitchevski wrote:
I am working under Linux actually.
Ok, then what kind of Linux ?
Also, tell us the version of Tomcat you are talking about, and whether
you installed it from the pre-packaged version offered by your Linux
version, or directly from the Tomcat website.
It matters, so
13 matches
Mail list logo