I'm trying to enable TLS (or SSL) in a Tomcat 5.5.29 server, on a
Windows XP machine.
Whatever I do, I always end up with a server that just delivers plain
HTML on port 443, and it doesn't even try to use TLS. That is, I can
connect to http://localhost:443/ and get the same as http://localhost/
a
There's an option somewhere to put the session ID into the URL.
You can store state information in the session. Be careful, a browser
with two windows will share the session between the two windows, so that
a user may get very confusing results when you store "currentpage" in
the session. Typicall
> I want to know does this Tomcat support HTTP/1.0 or HTTP/0.9
> protocol.
> Pleas help me make sure of it.
> I think the version of used HTTP protocol is
> determined by browser, is it right?
Tomcat still supports the older protocols. The browser determines the
version. Browsers have
The current configuration is correct in terms of security - the 'SYSTEM'
user is a limited account that has no access to the desktop nor shared
network resources.
Be warned that running a service under other credentials than the system
user is likely to lead to a less secure configuration, instead
Just redirect "as required".
http://myserver/login redirects to https://myserver/login, form submits
to the same page and when OK, it redirects to http://myserver/home or
whatever. You'll probably need to pass a 'secret' to the home link to
preserve the user's login, which might be a simple URI pa
In the days that I was forced to write my own HTTP server
implementation, I totally avoided Locale functions, to avoid this
particular type of problems. It's safer to create a few string arrays
with the proper (english) values and use those for day/month names.
Actually, I think the HTTP spec is si
The Last-Modified header is helping your server a lot, so don't just remove it.
It allows the client to cache the contents reliably, and only update the cache
when the server reports that the contents have changed.
For dynamically generated content, such as servlet data, Tomcat will not
append
: JSESSIONID=262FAFFC220AF50656BC67C1C1DD1331
> Cache-Control: max-age=0
> --> Response:
> Server: Apache-Coyote/1.1
> Last-Modified: Do, 17 Dez 2009 11:11:29 GMT
> Content-Type: text/javascript
> Transfer-Encoding: chunked
> Date: Thu, 17 Dec 2009 11:24:53 GMT
>
> Does a
I assume you mean 304 (Not modified) instead of 404 (Not found).
Simplest I can think of is to NOT put the "last-modified" header in your
response. Then the browser
won't send you an if-modified-since back.
On the other hand, if you can put a datestamp on the response - e.g. a
file date or by re
> > I am watching the log of Tomcat. I found after 20 minutes,
> the Tomcat
> > still create lots of new sessions. But the LoadRunner has
> stopped to
> > send request for 15 minutes.
Makes perfect sense to me.
The servlet times out on the DB connection, which may take up to a
minute or so
The reason is that "other" browsers use a media player component that
reconnects to the server. The "session" is linked to the browser
instance. As a result, the session is lost when the mediaplayer connects
to get the audio data.
Whap happens in "other" browsers is the equivalent of storing a
bo
ts.jsp?timestamp=1260252638867&contentid=137063&timemar
> k=20091110&index=4", this URL is used to pass parameters from
> one Jsp to another one. And we can get parameters with
> sentences like "request.getParameter("timestamp");
> request.getParameter(&
Put the session ID in the URL and it will work on all systems.
Alternatively, don't use sessions for the audio file.
> -Original Message-
> From: Peter Chen [mailto:peter.c...@aicent.com]
> Sent: maandag 07 december 2009 09:22
> To: users@tomcat.apache.org
> Subject: the Tomcat generat
Just an idea: What happens if you change your DB call into a "Sleep(30)"
or something similar? Does tomcat still misbehave then? (the 'retry'
could be related to something else than tomcat).
M
> -Original Message-
> From: Hadole, Nishant IN BOM SISL [mailto:nishant.had...@siemens.com]
>
...
> Without trying to send something back to the client, there is
> no way telling the client closed the window (or pressed
> reload or switched to another URL).
I would expect the socket to be closed, which can be detected at the
server side. The exceptions I can think of are the client cra
On unix (posix, linux) systems you can move anything even when in use.
Files that are open will remain open, and the application will continue
to use them. Problems will arise when the application attempts to open
new files, because then they have to be at the expected location.
If you really want
time.
M.
From: Caldarale, Charles R [mailto:chuck.caldar...@unisys.com]
> Sent: maandag 30 november 2009 15:54
> To: Tomcat Users List
> Subject: RE: AJP with HTTPD - Buffer Size on long URLs
>
> > From: Looijmans, Mike [mailto:mike.looijm...@oce.com]
> > Subject: RE:
> > SEVERE: Caught exception (java.lang.OutOfMemoryError:
> unable to create
> > new native thread) executing
> > org.apache.tomcat.util.net.leaderfollowerworkerthr...@958b36,
> >
> ...
> > Has anyone met this problem? Please give me some advice, thanks in
> > advance.
> >
> Well, it seem t
> Looijmans, Mike wrote:
> > The RFC specs a maximum URL size of 4k.
>
> Where precisely did you find that ?
RFC2068 (old HTTP/1.1 spec)
This message and attachment(s) are intended solely for use by the addressee and
may contain information that is privileged, confidential or o
The RFC specs a maximum URL size of 4k. That should be enough for everybody.
Note that you can mix and match as required: Use the URL portion of your
request to identify the target of the request, and put the additional data in
the POST body.
> -Original Message-
> From: André Warnier [
> I think so too. My personal doubt is still about how Tomcat
> would try map a request that comes in as "/", ""
> being variable and being NOT "myapp". Since it does not find
> a match with "/myapp", and since obviously there cannot be an
> infinity of "/webapps/" apps pre-config
> Let's refresh the issue :
>
> A request comes into Tomcat for a URL "/". It comes in
> either on port 80 or port 666. And you want it to be
> processed by the webapp at "/myapp/".
No: If it comes in at port 80, nothing "different" is supposed to
happen. So / should do whatever /x
> No. You want webapps/myapp to be treated as the ROOT context
> for a host.
> appBase="webapps/myapp" means look in the webapps/myapp
> directory to find contexts for this host. The ROOT context in
> that case would be webapps/myapp/ROOT
>
> As a general rule any configuration that boils down
he 400 response. There is also
nothing in the response or its headers to further explain what's wrong
with the request.
Mike.
> -----Original Message-
> From: Looijmans, Mike
> Sent: maandag 23 november 2009 14:06
> To: Tomcat Users List
> Subject: RE: Redirecting a port to a
> > I tried this, just to be able to make some progress on the actual
> > project, but it does not work as expected. I copied
> the part
> > and replaced:
> >
> >
> >
> > with
> >
> >
>
> You're telling the Host to look for war files or exploded app
> directories in "webapps
> Because you want different sets of webapps served on your
> different connectors, I *think* you'll need two different
> Services in your server.xml:
>
>
>for port 80
> for port 80
> for port 80
>for port 80, specifying base directory for your
> port 80 webapps
> fo
...
> Note that you'll end up with two independent copies of the
> servlet in your two webapp directories, and they won't share
> things like Sessions between them.
And, as I mentioned, I don't want that to happen.
> You might, however, be able to get what you want using a
> combination of htt
Hello,
After hours of googling and browsing documentation, i came to the conclusion
that what i want is either so trivial that everybody knows how to do it, or so
complicated that no one ever tried it...
I want to accomplish the following in Tomcat 5.5:
http://myserver:80/xxx just does what
28 matches
Mail list logo
