From what I can tell there's nothing (technically) wrong with what Tomcat
+ ISAPI Redirector is doing here.
What's actually happening here is that Tomcat internally only provides a
Content-Length header if it can determine the length of the content easily
(e.g. it's a static file) or the Servlet
Joe,
Tim is right. It's not necessary a problem of the webapp. If content is
dynamic and it doesn't make much sense to set content-length before the
response, when using AJP it's the responsibility of the web server to
handle the dynamic nature of the response. AJP itself knows how to
signal
My problem: Port 8443 won't open. But I can see port 8080.
Running Tomcat 5.0.28 on Mac OS 10.4.11 (no firewall yet).
I'm not using a self-assigned cert. I created a CSR request, got my
certs and have imported my certs in the following order using
Terminal. Everything I have researched
What I see below is a comment !-- -- block that does not
encompass both the beginning and ending Context elements. This would
fail if run through a XML validator. If the begin element is in the
comment, so should it's corresponding end element. Additionally be
careful you don't try to
I just realized what you posted was just a very narrow excerpt of the
comment block only. Could you provide a complete example?
--David
David Smith wrote:
What I see below is a comment !-- -- block that does not
encompass both the beginning and ending Context elements. This
would
Hi guys,
I want to serve a site with few graphics so I decided to use Tomcat 5.5 as my
server. But I'm having difficulty getting it to run on port 80. I read
http://www.ibm.com/developerworks/java/library/l-secjav.html and decided to try
xinetd. I added this to /etc/xinetd/:
# Redirects
verify the listen address is broadcasting on port 80 on the web-server
e.g.?netstat -a | grep
80Martin__Disclaimer and
confidentiality noteEverything in this e-mail and any attachments relates to
the official business of Sender. This transmission is
Check out your log see if there is any error info.
On Jan 5, 2008 11:29 PM, Chris Baty [EMAIL PROTECTED] wrote:
Hi guys,
I want to serve a site with few graphics so I decided to use Tomcat 5.5 as
my server. But I'm having difficulty getting it to run on port 80. I
read
This is what I get:
[1]+ Stopped man netstat
batybase:~# netstat -a | grep 80
tcp6 0 0 localhost:8005 *:* LISTEN
tcp6 0 0 *:8009 *:* LISTEN
tcp6 0 0 *:8180 *:*
Tim-Thanks for the comprehensive explanationI found this link helpful for CICS
transactions
http://publib.boulder.ibm.com/infocenter/cicsts/v3r1/index.jsp?topic=/com.ibm.cics.ts31.doc/dfhtl/topics/dfhtl_http11serverintro.htm
do you need IIS running..is there a way to perhaps use Apache with
In Joes case CICS seems to get used as an HTTP client, not an HTTP server.
Nevertheless the server page you found includes a link to
http://publib.boulder.ibm.com/infocenter/cicsts/v3r1/topic/com.ibm.cics.ts31.doc/dfhtl/topics/dfhtl_cwschunking.htm
that contains the following information:
Chris Baty wrote:
batybase:~# netstat -a | grep 80
tcp6 0 0 localhost:8005 *:* LISTEN
tcp6 0 0 *:8009 *:* LISTEN
tcp6 0 0 *:8180 *:* LISTEN
This doesn't
Hi Gregory,
the descriptions below work (at least) for TC 5.0/5.5/6.0.
Gregory Gerard schrieb:
I've got an F5 load balancer running version 9.3 of the software.
I've got several Tomcat installations behind it.
The F5 does all SSL and clear traffic as a reverse proxy, rewriting
headers as
Thanks! I'll give that a whirl. So you're saying that my marking it as
scheme='https' HttpServletRequest.isSecure() will respond with true?
Good to know about the multiple IPs... Didn't know that was legal but
makes sense.
Logging would be fine (though I don't know how the access log would
Sorry didn't read your post carefully enough. The access log thing is
OK, but about the redirect:
I've got an F5 load balancer running version 9.3 of the software.
I've got several Tomcat installations behind it.
The F5 does all SSL and clear traffic as a reverse proxy, rewriting
headers as
I've got an F5 load balancer running version 9.3 of the software.
I've got several Tomcat installations behind it.
The F5 does all SSL and clear traffic as a reverse proxy, rewriting
headers as needed for cookies and whatnot.
I have one connector on 8080 for the clear traffic.
My problem: I
In Tomcat 6.0.x you can do
Connector
port=8081
SSLEnabled=false
secure=true
scheme=https
...
In Tomcat 5.5.x you can write a Filter that creates a
HttpServletRequestWrapper, that returns true on isSecure, and https on
getScheme
or you can take a look at
Gregory Gerard schrieb:
Thanks! I'll give that a whirl. So you're saying that my marking it as
scheme='https' HttpServletRequest.isSecure() will respond with true?
No, sorry, see my second post. The attribute scheme is used when a
self-referencing redirect gets constructed. That's a way of
Chris Baty escribío:
Hi guys,
I want to serve a site with few graphics so I decided to use Tomcat 5.5 as my
server. But I'm having difficulty getting it to run on port 80. I read
http://www.ibm.com/developerworks/java/library/l-secjav.html and decided to try
xinetd. I added this to
Rainer Jung wrote:
Hi Gregory,
the descriptions below work (at least) for TC 5.0/5.5/6.0.
Gregory Gerard schrieb:
I've got an F5 load balancer running version 9.3 of the software.
I've got several Tomcat installations behind it.
The F5 does all SSL and clear traffic as a reverse proxy,
Gregory Gerard wrote:
Thanks! I'll give that a whirl. So you're saying that my marking it as
scheme='https' HttpServletRequest.isSecure() will respond with true?
Good to know about the multiple IPs... Didn't know that was legal but
makes sense.
Logging would be fine (though I don't know how
21 matches
Mail list logo
