You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by neal <ne...@yahoo.com> on 2003/02/16 00:41:48 UTC
Request to Fix Tomcat Standalone 302 redirect Issue
Has anyone considered fixing the following Tomcat standalone issue:
if a request is made to "www.xyz.com", tomcat auto redirects (per the
welcome files list) to "www.xyz.com/index.html". That's a 302 http
redirect. Aside from this being a very non-standard approach th handling
default files within a directory, it is extremely problematic when dealing
with Search Engines.
Search engines hate 302s and penalize most sites that utilize them,
particularly as their default page. Further in the case of Google, a page
rank is assigned to a url based upon inboind links. If the inboind links are
all to "www.xyz.com" and that url is just a redirect, you will never benefit
from the inbound links to your default url and never achieve a nigh ranking.
For these reasons this "feature" of tomcat renders the standalone http
server virtually commercially non-viable. This is a major concern for any
commercial site that reaps traffic from search engines, or from inbound
links.
I setup my site using tomcat standalone because I saw no reason to set it up
with Apache initially. But this one single reason is making me seriously
second guess that choice. Is this not somehting that can be easily fixed in
a future version? And if it can be fixed .... I would like to beg ...
grovel ... anything ... to have this changed. Otherwise, re-setting up with
apache is going to cost me a fair amount of $$$ and time at this point. :-\
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
Re: [5.0] Procrun problems / New loader
Posted by Remy Maucherat <re...@apache.org>.
mturk@mappingsoft.com wrote:
>>-----Original Message-----
>>From: Remy Maucherat [mailto:remm@apache.org]
>>Sent: 17. veljača 2003 9:38
>>To: Tomcat Developers List
>>Subject: Re: [5.0] Procrun problems / New loader
>>
>>jean-frederic clere wrote:
>>
>>>Remy Maucherat wrote:
>>>
>>>
>>>>I've switched (temporarily, maybe) away from JavaService to
>
> Procrun.
>
>>>>The problem is that I couldn't get it to work.
>>>>
>>>>In the install script, I'm using the following command:
>>>> ExecWait '"$INSTDIR\bin\tomcatw.exe" //IS//Tomcat5 --DisplayName
>>>>"Apache Tomcat @VERSION@" --Description "Apache Tomcat @VERSION@
>>>>Server http://jakarta.apache.org/tomcat" --Install
>>>>"$INSTDIR\bin\tomcat.exe" --ImagePath "$INSTDIR\bin\bootstrap.jar"
>>>>--StartupClass org.apache.catalina.startup.Bootstrap;main;start
>>>>--ShutdownClass org.apache.catalina.startup.Bootstrap;main;stop
>
> --Java
>
>>>>auto --JavaOptions
>>>>-Djava.endorsed.dirs="$INSTDIR\common\endorsed"#-
>>
>>Dcatalina.home="$INSTDIR"
>>
>>>>--StdOutputFile "$INSTDIR\logs\stdout.log" --StdErrorFile
>>>>"$INSTDIR\logs\stderr.log" --WorkingPath "$INSTDIR"'
>>>
>>>
>>>Have you try without the @VERSION@?
>>
>>It's an Ant token, so it gets replaced before invoking NSIS anyway.
>>The service parameters now gets populated correctly (I looked at the
>>source code to find out where they were going), but:
>>- err and out redirection doesn't seem to work (the console stays
>
> blank,
>
>>as do the logs, and all output goes into the console)
>
>
> Those can be used only if you redirect onother process. Try with "-Java
> java".
> Dunno how to redirect the console of the current process. Setting
> handles doesn't help. The only thing that can be used is API Hooking,
> but that's too much for now.
I was using -Java auto.
I thought it was supposed to be the same.
>>- procrunw still flashes a console when it's used; I thought it was
>>supposed not to
>
>
> It shouldn't. But the problem is that I made the wrong binaries using
> devcpp. Try with the lates build.
>
>
>>- WorkingPath doesn't seem to do anything
>
>
> Not when using JVM. For redirected app it sets the Working Directory
> when calling the CreateProcess.
That seems to be a plausible explanation. I had looked at the source,
and it seemed to be making the CreateProcess call using the right paramter.
>>- JavaOptions doesn't either :-(
>>
>
>
> Here is how it works for me:
>
> procrunw //IS//Tomcat4 --DisplayName "Tomcat 4.1.19" --Description
> "Tomcat 4.1.19 LE JDK 1.4 http://jakarta.apache.org" --ImagePath
> "c:\devtools\tomcat\41\bin\bootstrap.jar" --StartupClass
> org.apache.catalina.startup.Bootstrap;main;start --ShutdownClass
> org.apache.catalina.startup.Bootstrap;main;stop --Java auto
> --JavaOptions
> -Dcatalina.home=c:\devtools\tomcat\41#-Xmx128M#-Dtomcat.home=c:\devtools
> \tomcat\41
>
>
> Perhaps you exceeded the command line length. Try using the
> Procrunw //IS//Tomcat <minimum params> (ServiceName, DisplayName,
> ImagePath, and Install).
> Then
> Procrunw //US//Tomcat <extra params> (update service changing or adding
> params.)
Well, I checked with the registry, and everything gets registered ok
with one single call. Update also works good.
> You can call the //US as many times as you wish.
>
> Also check if some installation params that NSIS process have emedded
> spaces. In that case you'll need to quote that params.
> --JavaOptions needs the next argument as single string so it need to be
> quoted.
>
> "--Dcatalina.home=\"some location\"#etc..."
Yes, I sort of figured that out. I tried hacking the value in the
registry without much success.
> How and are the params set correctly, can be seen in the registry:
> HKLM\\SOFTWARE\\Apache Software Foundation\\Process Runner
> 1.0\\ServiceName\\Parameters.
>
> The JavaOptions is MULTI_SZ, and you can check the params there.
Yes, I had already found out everything was there.
Remy
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
Re: [5.0] Procrun problems / New loader
Posted by jean-frederic clere <jf...@fujitsu-siemens.com>.
Remy Maucherat wrote:
> mturk@mappingsoft.com wrote:
>
>>
>>> -----Original Message-----
>>> From: jean-frederic clere
>>> [mailto:jfrederic.clere@fujitsu-siemens.com] Sent: 17. veljača 2003
>>> 12:14
>>> To: Tomcat Developers List
>>> Subject: Re: [5.0] Procrun problems / New loader
>>>
>>> #ifdefs No...
>>> I remember doing this in instmain.c
>>> (jakarta-commons-sandbox/daemon/src/native/nt/service). Should I
>>> copy/adapte this code to procrun?
>>>
>>
>>
>> Well, that was just an idea (using ifdefs), you can use OS guessing
>> inside the procrun itself.
>>
>> In that case you'll need to make something like
>> procrun_install_service9x and
>> call that instead procrun_install_service. Also you'll need the wrap the
>> update_service and delete_service
>> functions.
>>
>> I would like to see that as a new functions, not just to support the 9x
>> inside the existing one.
>>
>> Everthing else should work as is, so you are wellcome to copy that from
>> instmain.
>
>
> All that sounds great :)
I have just committed the support for win9x but I have not tested it yet.
>
> There's a puzzling side effect to procrun, though: Ant fails to start
> the Java compiler in "fork" mode. If I disable forking javac, it works.
> Does the Java process lose the right to fork other processes when it is
> run through procrun ?
> That would be really weird, because the JNI based JavaService didn't
> have that problem (AFAIK).
>
> Remy
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
Re: [5.0] Procrun problems / New loader
Posted by Remy Maucherat <re...@apache.org>.
mturk@mappingsoft.com wrote:
>
>>-----Original Message-----
>>From: Remy Maucherat [mailto:remm@apache.org]
>>
>>There's a puzzling side effect to procrun, though: Ant fails to start
>>the Java compiler in "fork" mode. If I disable forking javac,
>>it works. Does the Java process lose the right to fork other
>>processes when it is
>>run through procrun ?
>>That would be really weird, because the JNI based JavaService didn't
>>have that problem (AFAIK).
>>
>
>
> Try running in console mode: "procrun.exe //TS//Tomcat5".
That's with the GT option. Does that make a difference ?
I'll check it more (but right after I fix a minor bug in the mapper).
> If that's OK then it's a security issue thought. Also what Java and OS?
> Mine is Sun's 1.4.1 and WIN2K Server.
1.4.1 + XP
> I'm running TC 4.1.20 and web.xml has set:
>
> <init-param>
>
> <param-name>development</param-name>
>
> <param-value>false</param-value>
>
> </init-param>
I'm using the fork init-param to fix it:
<init-param>
<param-name>fork</param-name>
<param-value>false</param-value>
</init-param>
The error page is the one you get when the compiler is not found.
> For each jsp I see that the javac is launched under SYSTEM account. So
> it works.
> Didn't test with 5.0 but I think that there isn't much difference for
> that case.
>
>
> There is other problem with the running TC using redirected Java, and
> that is the
> lack of gracefull shutdown option. I'm working on that right now.
> It will enable JVM invocation of Bootstrap with (stop or stopd) in that
> case if enabled.
It's ok if it just sends a term signal to the VM (there's a shutdown hook).
Remy
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
Re: [5.0] Procrun problems / New loader
Posted by Remy Maucherat <re...@apache.org>.
mturk@mappingsoft.com wrote:
>
>>-----Original Message-----
>>From: Remy Maucherat [mailto:remm@apache.org]
>>
>>There's a puzzling side effect to procrun, though: Ant fails to start
>>the Java compiler in "fork" mode. If I disable forking javac,
>>it works. Does the Java process lose the right to fork other
>>processes when it is
>>run through procrun ?
>>That would be really weird, because the JNI based JavaService didn't
>>have that problem (AFAIK).
>>
>
>
> Try running in console mode: "procrun.exe //TS//Tomcat5".
> If that's OK then it's a security issue thought. Also what Java and OS?
> Mine is Sun's 1.4.1 and WIN2K Server.
TS does the same as GT. (ie, it fails with fork being true, which is the
default, and works with fork being false).
Remy
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
RE: [5.0] Procrun problems / New loader
Posted by mt...@mappingsoft.com.
> -----Original Message-----
> From: Remy Maucherat [mailto:remm@apache.org]
>
> There's a puzzling side effect to procrun, though: Ant fails to start
> the Java compiler in "fork" mode. If I disable forking javac,
> it works. Does the Java process lose the right to fork other
> processes when it is
> run through procrun ?
> That would be really weird, because the JNI based JavaService didn't
> have that problem (AFAIK).
>
Try running in console mode: "procrun.exe //TS//Tomcat5".
If that's OK then it's a security issue thought. Also what Java and OS?
Mine is Sun's 1.4.1 and WIN2K Server.
I'm running TC 4.1.20 and web.xml has set:
<init-param>
<param-name>development</param-name>
<param-value>false</param-value>
</init-param>
For each jsp I see that the javac is launched under SYSTEM account. So
it works.
Didn't test with 5.0 but I think that there isn't much difference for
that case.
There is other problem with the running TC using redirected Java, and
that is the
lack of gracefull shutdown option. I'm working on that right now.
It will enable JVM invocation of Bootstrap with (stop or stopd) in that
case if enabled.
MT.
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
Re: [5.0] Procrun problems / New loader
Posted by Remy Maucherat <re...@apache.org>.
mturk@mappingsoft.com wrote:
>
>>-----Original Message-----
>>From: jean-frederic clere
>>[mailto:jfrederic.clere@fujitsu-siemens.com]
>>Sent: 17. veljača 2003 12:14
>>To: Tomcat Developers List
>>Subject: Re: [5.0] Procrun problems / New loader
>>
>>#ifdefs No...
>>I remember doing this in instmain.c
>>(jakarta-commons-sandbox/daemon/src/native/nt/service).
>>Should I copy/adapte
>>this code to procrun?
>>
>
>
> Well, that was just an idea (using ifdefs), you can use OS guessing
> inside the procrun itself.
>
> In that case you'll need to make something like
> procrun_install_service9x and
> call that instead procrun_install_service. Also you'll need the wrap the
> update_service and delete_service
> functions.
>
> I would like to see that as a new functions, not just to support the 9x
> inside the existing one.
>
> Everthing else should work as is, so you are wellcome to copy that from
> instmain.
All that sounds great :)
There's a puzzling side effect to procrun, though: Ant fails to start
the Java compiler in "fork" mode. If I disable forking javac, it works.
Does the Java process lose the right to fork other processes when it is
run through procrun ?
That would be really weird, because the JNI based JavaService didn't
have that problem (AFAIK).
Remy
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
Re: [5.0] Procrun problems / New loader
Posted by jean-frederic clere <jf...@fujitsu-siemens.com>.
mturk@mappingsoft.com wrote:
>
>>-----Original Message-----
>>From: jean-frederic clere
>>[mailto:jfrederic.clere@fujitsu-siemens.com]
>>Sent: 17. veljača 2003 12:14
>>To: Tomcat Developers List
>>Subject: Re: [5.0] Procrun problems / New loader
>>
>>#ifdefs No...
>>I remember doing this in instmain.c
>>(jakarta-commons-sandbox/daemon/src/native/nt/service).
>>Should I copy/adapte
>>this code to procrun?
>>
>
>
> Well, that was just an idea (using ifdefs), you can use OS guessing
> inside the procrun itself.
>
> In that case you'll need to make something like
> procrun_install_service9x and
> call that instead procrun_install_service. Also you'll need the wrap the
> update_service and delete_service
> functions.
>
> I would like to see that as a new functions, not just to support the 9x
> inside the existing one.
That is what instmain.c is doing.
+++
if (isWindowsNT())
done = InstallSvcNT(szExePath);
else
done = InstallSvc(szExePath);
+++
And
+++
if (isWindowsNT())
done = RemoveSvcNT();
else
done = RemoveSvc();
+++
I do not have update_service for 9x.
>
> Everthing else should work as is, so you are wellcome to copy that from
> instmain.
I will do it ASAP...
>
> MT.
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
RE: [5.0] Procrun problems / New loader
Posted by mt...@mappingsoft.com.
> -----Original Message-----
> From: jean-frederic clere
> [mailto:jfrederic.clere@fujitsu-siemens.com]
> Sent: 17. veljača 2003 12:14
> To: Tomcat Developers List
> Subject: Re: [5.0] Procrun problems / New loader
>
> #ifdefs No...
> I remember doing this in instmain.c
> (jakarta-commons-sandbox/daemon/src/native/nt/service).
> Should I copy/adapte
> this code to procrun?
>
Well, that was just an idea (using ifdefs), you can use OS guessing
inside the procrun itself.
In that case you'll need to make something like
procrun_install_service9x and
call that instead procrun_install_service. Also you'll need the wrap the
update_service and delete_service
functions.
I would like to see that as a new functions, not just to support the 9x
inside the existing one.
Everthing else should work as is, so you are wellcome to copy that from
instmain.
MT.
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
Re: [5.0] Procrun problems / New loader
Posted by jean-frederic clere <jf...@fujitsu-siemens.com>.
mturk@mappingsoft.com wrote:
>
>>-----Original Message-----
>>From: Remy Maucherat [mailto:remm@apache.org]
>>Sent: 17. veljača 2003 11:28
>>To: Tomcat Developers List
>>Subject: Re: [5.0] Procrun problems / New loader
>>
>>
>>mturk@mappingsoft.com wrote:
>>
>>>Those can be used only if you redirect onother process. Try with
>>>"-Java java".
>>
>>Ok, it's the magic parameter indeed :) Rereading the readme.txt, it
>>looks like it's supposed to be equivalent to "auto".
>>
>
>
>
>
>
>>Another question: Can I use procrun on 9x ?
>>There's a duplication of functionality between procrun and
>>the laucher.
>>Should procrun call the laucher, which then calls the launcher ? It
>>seems like a waste of resources, so maybe procrun should go
>>directly to
>>Tomcat ;-)
>>
>
>
> It could, need some API cheching. There is no CreateRemoteThread API,
> and Services alltogether.
>
> The simplest would be using some #ifdefs and and another build.
> If the nsis installer can distinguish the host OS, than we can
> make something like procrun9x.
#ifdefs No...
I remember doing this in instmain.c
(jakarta-commons-sandbox/daemon/src/native/nt/service). Should I copy/adapte
this code to procrun?
>
>
> MT.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
Repost: [4.1.20] Stability rating
Posted by Remy Maucherat <re...@apache.org>.
Remy Maucherat wrote:
> I would like comments on bug 17049 before deciding what to do with 4.1.20.
>
> If this turns out to be a relatively minor issue, I would be ok with
> releasing 4.1.20 as a beta, and would propose a vote.
>
> For 4.1.21, there are apparently some patches for better taglib handling
> to be integrated in JspC. Other than that, it looks good enough to me.
This is a serious bug in Jasper, and I think may have been introduced by
Jan's commit attached here.
I will try to find time to look into the issue.
Remy
luehe 2003/01/16 17:21:06
Modified: jasper2/src/share/org/apache/jasper/compiler Tag:
tomcat_4_branch Generator.java
Log:
Fixed 16181: JspWriter not restored properly when exception thrown in
a tag's body content
Revision Changes Path
No revision
No revision
1.35.2.17 +12 -12
jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/compiler/Generator.java
Index: Generator.java
===================================================================
RCS file:
/home/cvs/jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/compiler/Generator.java,v
retrieving revision 1.35.2.16
retrieving revision 1.35.2.17
diff -u -r1.35.2.16 -r1.35.2.17
--- Generator.java 17 Jan 2003 00:51:23 -0000 1.35.2.16
+++ Generator.java 17 Jan 2003 01:21:06 -0000 1.35.2.17
@@ -545,7 +545,7 @@
private Hashtable tagVarNumbers;
private String parent;
- private String pushBodyCount;
+ private String pushBodyCountVar;
private ServletWriter out;
private MethodsBuffer methodsBuffer;
@@ -1177,17 +1177,17 @@
String tmpParent = parent;
parent = tagHandlerVar;
- String tmpPushBodyCount = null;
+ String tmpPushBodyCountVar = null;
if (n.implementsTryCatchFinally()) {
- tmpPushBodyCount = pushBodyCount;
- pushBodyCount = tagPushBodyCountVar;
+ tmpPushBodyCountVar = pushBodyCountVar;
+ pushBodyCountVar = tagPushBodyCountVar;
}
visitBody(n);
parent = tmpParent;
if (n.implementsTryCatchFinally()) {
- pushBodyCount = tmpPushBodyCount;
+ pushBodyCountVar = tmpPushBodyCountVar;
}
generateCustomEnd(n, tagHandlerVar, tagEvalVar,
@@ -1390,8 +1390,8 @@
if (n.implementsTryCatchFinally()) {
out.printin(tagPushBodyCountVar);
out.println("++;");
- } else if (pushBodyCount != null) {
- out.printin(pushBodyCount);
+ } else if (pushBodyCountVar != null) {
+ out.printin(pushBodyCountVar);
out.println("++;");
}
out.printil("out = _bc;");
@@ -1458,8 +1458,8 @@
if (n.implementsTryCatchFinally()) {
out.printin(tagPushBodyCountVar);
out.println("--;");
- } else if (pushBodyCount != null) {
- out.printin(pushBodyCount);
+ } else if (pushBodyCountVar != null) {
+ out.printin(pushBodyCountVar);
out.println("--;");
}
out.popIndent();
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
Re: [4.1.21] New tag and upcoming vote
Posted by "Jess M. Holle" <je...@ptc.com>.
Remy Maucherat wrote:
> Hi,
>
> Since the needed fix to Jasper was integrated in the 4.1.x branch, I
> plan to tag and release a 4.1.21 version of Tomcat (and I hope it will
> then be voted as a beta :) ).
>
> Since the amount of changes between 4.1.20 and 4.1.21 is minimal, I
> plan to post the stability vote on the next day.
Any hope for another "stable" release one of these weeks?
--
Jess Holle
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
[4.1.21] New tag and upcoming vote
Posted by Remy Maucherat <re...@apache.org>.
Hi,
Since the needed fix to Jasper was integrated in the 4.1.x branch, I
plan to tag and release a 4.1.21 version of Tomcat (and I hope it will
then be voted as a beta :) ).
Since the amount of changes between 4.1.20 and 4.1.21 is minimal, I plan
to post the stability vote on the next day.
Thanks,
Remy
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
[4.1.20] Stability rating
Posted by Remy Maucherat <re...@apache.org>.
I would like comments on bug 17049 before deciding what to do with 4.1.20.
If this turns out to be a relatively minor issue, I would be ok with
releasing 4.1.20 as a beta, and would propose a vote.
For 4.1.21, there are apparently some patches for better taglib handling
to be integrated in JspC. Other than that, it looks good enough to me.
Thanks,
Remy
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
RE: [5.0] Procrun problems / New loader
Posted by mt...@mappingsoft.com.
> -----Original Message-----
> From: Remy Maucherat [mailto:remm@apache.org]
> >
> > The simplest would be using some #ifdefs and and another
> build. If the
> > nsis installer can distinguish the host OS, than we can
> make something
> > like procrun9x.
>
> That's doable. I don't know if it's really useful, though.
> Or we decide we should stop caring about Win 9x for the installer.
>
+1. One who is enthusiast enough to use the TC on DOS box is certainly
capable of setting that up ;-).
MT.
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
Re: [5.0] Procrun problems / New loader
Posted by Remy Maucherat <re...@apache.org>.
mturk@mappingsoft.com wrote:
> It could, need some API cheching. There is no CreateRemoteThread API,
> and Services alltogether.
>
> The simplest would be using some #ifdefs and and another build.
> If the nsis installer can distinguish the host OS, than we can
> make something like procrun9x.
That's doable. I don't know if it's really useful, though.
Or we decide we should stop caring about Win 9x for the installer.
Remy
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
RE: [5.0] Procrun problems / New loader
Posted by mt...@mappingsoft.com.
> -----Original Message-----
> From: Remy Maucherat [mailto:remm@apache.org]
> Sent: 17. veljača 2003 11:28
> To: Tomcat Developers List
> Subject: Re: [5.0] Procrun problems / New loader
>
>
> mturk@mappingsoft.com wrote:
> > Those can be used only if you redirect onother process. Try with
> > "-Java java".
>
> Ok, it's the magic parameter indeed :) Rereading the readme.txt, it
> looks like it's supposed to be equivalent to "auto".
>
> Another question: Can I use procrun on 9x ?
> There's a duplication of functionality between procrun and
> the laucher.
> Should procrun call the laucher, which then calls the launcher ? It
> seems like a waste of resources, so maybe procrun should go
> directly to
> Tomcat ;-)
>
It could, need some API cheching. There is no CreateRemoteThread API,
and Services alltogether.
The simplest would be using some #ifdefs and and another build.
If the nsis installer can distinguish the host OS, than we can
make something like procrun9x.
MT.
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
Re: [5.0] Procrun problems / New loader
Posted by Remy Maucherat <re...@apache.org>.
mturk@mappingsoft.com wrote:
> Those can be used only if you redirect onother process. Try with "-Java
> java".
Ok, it's the magic parameter indeed :) Rereading the readme.txt, it
looks like it's supposed to be equivalent to "auto".
Another question: Can I use procrun on 9x ?
There's a duplication of functionality between procrun and the laucher.
Should procrun call the laucher, which then calls the launcher ? It
seems like a waste of resources, so maybe procrun should go directly to
Tomcat ;-)
Remy
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
RE: [5.0] Procrun problems / New loader
Posted by mt...@mappingsoft.com.
> -----Original Message-----
> From: Remy Maucherat [mailto:remm@apache.org]
> Sent: 17. veljača 2003 9:38
> To: Tomcat Developers List
> Subject: Re: [5.0] Procrun problems / New loader
>
> jean-frederic clere wrote:
> > Remy Maucherat wrote:
> >
> >> I've switched (temporarily, maybe) away from JavaService to
Procrun.
> >> The problem is that I couldn't get it to work.
> >>
> >> In the install script, I'm using the following command:
> >> ExecWait '"$INSTDIR\bin\tomcatw.exe" //IS//Tomcat5 --DisplayName
> >> "Apache Tomcat @VERSION@" --Description "Apache Tomcat @VERSION@
> >> Server http://jakarta.apache.org/tomcat" --Install
> >> "$INSTDIR\bin\tomcat.exe" --ImagePath "$INSTDIR\bin\bootstrap.jar"
> >> --StartupClass org.apache.catalina.startup.Bootstrap;main;start
> >> --ShutdownClass org.apache.catalina.startup.Bootstrap;main;stop
--Java
> >> auto --JavaOptions
> >> -Djava.endorsed.dirs="$INSTDIR\common\endorsed"#-
> Dcatalina.home="$INSTDIR"
> >> --StdOutputFile "$INSTDIR\logs\stdout.log" --StdErrorFile
> >> "$INSTDIR\logs\stderr.log" --WorkingPath "$INSTDIR"'
> >
> >
> > Have you try without the @VERSION@?
>
> It's an Ant token, so it gets replaced before invoking NSIS anyway.
> The service parameters now gets populated correctly (I looked at the
> source code to find out where they were going), but:
> - err and out redirection doesn't seem to work (the console stays
blank,
> as do the logs, and all output goes into the console)
Those can be used only if you redirect onother process. Try with "-Java
java".
Dunno how to redirect the console of the current process. Setting
handles doesn't help. The only thing that can be used is API Hooking,
but that's too much for now.
> - procrunw still flashes a console when it's used; I thought it was
> supposed not to
It shouldn't. But the problem is that I made the wrong binaries using
devcpp. Try with the lates build.
> - WorkingPath doesn't seem to do anything
Not when using JVM. For redirected app it sets the Working Directory
when calling the CreateProcess.
> - JavaOptions doesn't either :-(
>
Here is how it works for me:
procrunw //IS//Tomcat4 --DisplayName "Tomcat 4.1.19" --Description
"Tomcat 4.1.19 LE JDK 1.4 http://jakarta.apache.org" --ImagePath
"c:\devtools\tomcat\41\bin\bootstrap.jar" --StartupClass
org.apache.catalina.startup.Bootstrap;main;start --ShutdownClass
org.apache.catalina.startup.Bootstrap;main;stop --Java auto
--JavaOptions
-Dcatalina.home=c:\devtools\tomcat\41#-Xmx128M#-Dtomcat.home=c:\devtools
\tomcat\41
Perhaps you exceeded the command line length. Try using the
Procrunw //IS//Tomcat <minimum params> (ServiceName, DisplayName,
ImagePath, and Install).
Then
Procrunw //US//Tomcat <extra params> (update service changing or adding
params.)
You can call the //US as many times as you wish.
Also check if some installation params that NSIS process have emedded
spaces. In that case you'll need to quote that params.
--JavaOptions needs the next argument as single string so it need to be
quoted.
"--Dcatalina.home=\"some location\"#etc..."
How and are the params set correctly, can be seen in the registry:
HKLM\\SOFTWARE\\Apache Software Foundation\\Process Runner
1.0\\ServiceName\\Parameters.
The JavaOptions is MULTI_SZ, and you can check the params there.
MT.
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
Re: [5.0] Procrun problems / New loader
Posted by Remy Maucherat <re...@apache.org>.
jean-frederic clere wrote:
> Remy Maucherat wrote:
>
>> Hi,
>>
>> I've switched (temporarily, maybe) away from JavaService to Procrun.
>> The problem is that I couldn't get it to work.
>>
>> In the install script, I'm using the following command:
>> ExecWait '"$INSTDIR\bin\tomcatw.exe" //IS//Tomcat5 --DisplayName
>> "Apache Tomcat @VERSION@" --Description "Apache Tomcat @VERSION@
>> Server http://jakarta.apache.org/tomcat" --Install
>> "$INSTDIR\bin\tomcat.exe" --ImagePath "$INSTDIR\bin\bootstrap.jar"
>> --StartupClass org.apache.catalina.startup.Bootstrap;main;start
>> --ShutdownClass org.apache.catalina.startup.Bootstrap;main;stop --Java
>> auto --JavaOptions
>> -Djava.endorsed.dirs="$INSTDIR\common\endorsed"#-Dcatalina.home="$INSTDIR"
>> --StdOutputFile "$INSTDIR\logs\stdout.log" --StdErrorFile
>> "$INSTDIR\logs\stderr.log" --WorkingPath "$INSTDIR"'
>
>
> Have you try without the @VERSION@?
It's an Ant token, so it gets replaced before invoking NSIS anyway.
The service parameters now gets populated correctly (I looked at the
source code to find out where they were going), but:
- err and out redirection doesn't seem to work (the console stays blank,
as do the logs, and all output goes into the console)
- procrunw still flashes a console when it's used; I thought it was
supposed not to
- WorkingPath doesn't seem to do anything
- JavaOptions doesn't either :-(
If I call the test service mode from the right directory (the Catalina
home), then it works ok.
Additionally, it seems that the daemon must block until stop is called
to work.
Remy
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
Re: [5.0] Procrun problems / New loader
Posted by jean-frederic clere <jf...@fujitsu-siemens.com>.
Remy Maucherat wrote:
> Hi,
>
> I've switched (temporarily, maybe) away from JavaService to Procrun.
> The problem is that I couldn't get it to work.
>
> In the install script, I'm using the following command:
> ExecWait '"$INSTDIR\bin\tomcatw.exe" //IS//Tomcat5 --DisplayName
> "Apache Tomcat @VERSION@" --Description "Apache Tomcat @VERSION@ Server
> http://jakarta.apache.org/tomcat" --Install "$INSTDIR\bin\tomcat.exe"
> --ImagePath "$INSTDIR\bin\bootstrap.jar" --StartupClass
> org.apache.catalina.startup.Bootstrap;main;start --ShutdownClass
> org.apache.catalina.startup.Bootstrap;main;stop --Java auto
> --JavaOptions
> -Djava.endorsed.dirs="$INSTDIR\common\endorsed"#-Dcatalina.home="$INSTDIR"
> --StdOutputFile "$INSTDIR\logs\stdout.log" --StdErrorFile
> "$INSTDIR\logs\stderr.log" --WorkingPath "$INSTDIR"'
Have you try without the @VERSION@?
>
> I believe this is correct, and using the test mode sort of works (except
> that the console output doesn't get redirected). Trying to run the
> service doesn't work at all, and looking in the registry, it doesn't
> seem to have the needed parameters (so I wonder how the test mode does
> work).
>
> Also, Procrun doesn't seem to be designed to handle Tomcat in service
> mode (that is, where Tomcat doesn't block and wait for a shutdown command).
>
> Mladen, I think I need some help :)
>
> Other that that, there are now too many ways to start Tomcat in
> standalone mode:
> - Bootstrap
> - The launcher
> - JMX
>
> I think the most compelling is to use the launcher + JMX (and allow JMX
> only also). Basically, in the Windows distribution, there are some
> incosistencies, as the scripts use the launcher, while the service uses
> direct invocation of Bootstrap.
>
> I can't do those changes alone.
> Comments ?
Java code of daemon:
jakarta-commons-sandbox/daemon/src/java/org/apache/commons/daemon
Java code of launcher:
jakarta-commons-sandbox/daemon/src/java/org/apache/commons/launcher
C code of procrun:
jakarta-commons-sandbox/daemon/src/native/nt/procrun
C code of daemon:
jakarta-commons-sandbox/daemon/src/native (except nt/procrun)
I am using daemon to start Tomcat as normal user but listening on port 80 on Linux.
I am also using daemon (with cygwin) to run Tomcat on windoze but I am thinking
to change to procrun for that platfrom.
For the moment I have not enough time to look to launcher nor JMX.
>
> Remy
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
[5.0] Procrun problems / New loader
Posted by Remy Maucherat <re...@apache.org>.
Hi,
I've switched (temporarily, maybe) away from JavaService to Procrun.
The problem is that I couldn't get it to work.
In the install script, I'm using the following command:
ExecWait '"$INSTDIR\bin\tomcatw.exe" //IS//Tomcat5 --DisplayName
"Apache Tomcat @VERSION@" --Description "Apache Tomcat @VERSION@ Server
http://jakarta.apache.org/tomcat" --Install "$INSTDIR\bin\tomcat.exe"
--ImagePath "$INSTDIR\bin\bootstrap.jar" --StartupClass
org.apache.catalina.startup.Bootstrap;main;start --ShutdownClass
org.apache.catalina.startup.Bootstrap;main;stop --Java auto
--JavaOptions
-Djava.endorsed.dirs="$INSTDIR\common\endorsed"#-Dcatalina.home="$INSTDIR"
--StdOutputFile "$INSTDIR\logs\stdout.log" --StdErrorFile
"$INSTDIR\logs\stderr.log" --WorkingPath "$INSTDIR"'
I believe this is correct, and using the test mode sort of works (except
that the console output doesn't get redirected). Trying to run the
service doesn't work at all, and looking in the registry, it doesn't
seem to have the needed parameters (so I wonder how the test mode does
work).
Also, Procrun doesn't seem to be designed to handle Tomcat in service
mode (that is, where Tomcat doesn't block and wait for a shutdown command).
Mladen, I think I need some help :)
Other that that, there are now too many ways to start Tomcat in
standalone mode:
- Bootstrap
- The launcher
- JMX
I think the most compelling is to use the launcher + JMX (and allow JMX
only also). Basically, in the Windows distribution, there are some
incosistencies, as the scripts use the launcher, while the service uses
direct invocation of Bootstrap.
I can't do those changes alone.
Comments ?
Remy
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
Re: Request to Fix Tomcat Standalone 302 redirect Issue
Posted by Tim Funk <fu...@joedog.org>.
I thought I had an answer but the more I delved into the code the more I
realized I should shut up. (I rather give no reply than a wrong reply)
Now going back to read more code.
----
-Tim
I'm starting to hate snow (after shoveling over 2 feet with more coming)
Donald Ball wrote:
> Tim Funk wrote:
>
>> A patch (which I didn't look at yet) could introduce the following:
>> - Bypassing a security contraints, eg:index.jsp is protected but / isn't
>> - Vulnerabilities - Through a wacky optimizations, other pages might
>> get accidently exposed
>
>
>
> Just curious... I assume the patch uses RequestDispatcher.forward to
> handle the request, right? But these checks should already be done by
> the RequestDispatcher, otherwise _anything_ that uses rd.forward could
> break security. So if we trust rd, what's the issue? If we don't, um,
> why _not_?
>
> - donald
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
Re: Request to Fix Tomcat Standalone 302 redirect Issue
Posted by "Craig R. McClanahan" <cr...@apache.org>.
On Mon, 17 Feb 2003, Donald Ball wrote:
> Date: Mon, 17 Feb 2003 11:44:16 -0500
> From: Donald Ball <db...@rhoworld.com>
> Reply-To: Tomcat Developers List <to...@jakarta.apache.org>
> To: Tomcat Developers List <to...@jakarta.apache.org>
> Subject: Re: Request to Fix Tomcat Standalone 302 redirect Issue
>
> Tim Funk wrote:
>
> > A patch (which I didn't look at yet) could introduce the following:
> > - Bypassing a security contraints, eg:index.jsp is protected but / isn't
> > - Vulnerabilities - Through a wacky optimizations, other pages might
> > get accidently exposed
>
>
> Just curious... I assume the patch uses RequestDispatcher.forward to
> handle the request, right? But these checks should already be done by
> the RequestDispatcher, otherwise _anything_ that uses rd.forward could
> break security. So if we trust rd, what's the issue? If we don't, um,
> why _not_?
>
Security constraints are only checked on the original request URL, not on
RD.forward or RD.include calls -- the container assumes that the
application knows what it is doing in executing those calls within the
app.
If the container wants to use RD (or the internal equivalent) to implement
welcome file support, or other container level features like error files,
it had better pay attention to the security constraints.
> - donald
Craig
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
Re: Request to Fix Tomcat Standalone 302 redirect Issue
Posted by Donald Ball <db...@rhoworld.com>.
Tim Funk wrote:
> A patch (which I didn't look at yet) could introduce the following:
> - Bypassing a security contraints, eg:index.jsp is protected but / isn't
> - Vulnerabilities - Through a wacky optimizations, other pages might
> get accidently exposed
Just curious... I assume the patch uses RequestDispatcher.forward to
handle the request, right? But these checks should already be done by
the RequestDispatcher, otherwise _anything_ that uses rd.forward could
break security. So if we trust rd, what's the issue? If we don't, um,
why _not_?
- donald
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
Re: Request to Fix Tomcat Standalone 302 redirect Issue
Posted by Tim Funk <fu...@joedog.org>.
A patch (which I didn't look at yet) could introduce the following:
- Bypassing a security contraints, eg:index.jsp is protected but / isn't
- Vulnerabilities - Through a wacky optimizations, other pages might get
accidently exposed
- It breaks the spec for a different case
Odds are - none of these happen with the patches, but when others don't
review these conditions is when 'oops' slip through.
-Tim
neal wrote:
> What are the security problems and why doesn't Apache or other major web
> servers have this problem (or do they)?
>
> If this is made optional (with the default turned off) is the problem with
> it breaking an app ... really a problem?
>
>
>
> -----Original Message-----
> From: Remy Maucherat [mailto:remm@apache.org]
> Sent: Monday, February 17, 2003 1:58 AM
> To: Tomcat Developers List
> Subject: Re: Request to Fix Tomcat Standalone 302 redirect Issue
>
>
> Bill Barker wrote:
>
>>----- Original Message -----
>>From: "neal" <ne...@yahoo.com>
>>To: "Tomcat Developers List" <to...@jakarta.apache.org>
>>Sent: Sunday, February 16, 2003 8:00 PM
>>Subject: RE: Request to Fix Tomcat Standalone 302 redirect Issue
>>
>>
>>
>>
>>>So it *will* be in tomcat 5?
>>>
>>>My head is spinning...so confusing.
>>>
>>>How does one access o.a.t.u.http.mapper.Mapper? Is this something that
>>
>>will
>>
>>
>>>be configurable via web.xml?
>>>
>>
>>
>>It will be in configurable in 'server.xml' (or, at least it will be when I
>>do my next commit :).
>
>
> Good, the code looks like as if I had written it myself :)
>
> However, it poses the usual security problems, and breaks the admin webapp.
>
> Remy
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
RE: Request to Fix Tomcat Standalone 302 redirect Issue
Posted by neal <ne...@yahoo.com>.
What are the security problems and why doesn't Apache or other major web
servers have this problem (or do they)?
If this is made optional (with the default turned off) is the problem with
it breaking an app ... really a problem?
-----Original Message-----
From: Remy Maucherat [mailto:remm@apache.org]
Sent: Monday, February 17, 2003 1:58 AM
To: Tomcat Developers List
Subject: Re: Request to Fix Tomcat Standalone 302 redirect Issue
Bill Barker wrote:
> ----- Original Message -----
> From: "neal" <ne...@yahoo.com>
> To: "Tomcat Developers List" <to...@jakarta.apache.org>
> Sent: Sunday, February 16, 2003 8:00 PM
> Subject: RE: Request to Fix Tomcat Standalone 302 redirect Issue
>
>
>
>>So it *will* be in tomcat 5?
>>
>>My head is spinning...so confusing.
>>
>>How does one access o.a.t.u.http.mapper.Mapper? Is this something that
>
> will
>
>>be configurable via web.xml?
>>
>
>
> It will be in configurable in 'server.xml' (or, at least it will be when I
> do my next commit :).
Good, the code looks like as if I had written it myself :)
However, it poses the usual security problems, and breaks the admin webapp.
Remy
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
Re: Request to Fix Tomcat Standalone 302 redirect Issue
Posted by Remy Maucherat <re...@apache.org>.
Bill Barker wrote:
> ----- Original Message -----
> From: "neal" <ne...@yahoo.com>
> To: "Tomcat Developers List" <to...@jakarta.apache.org>
> Sent: Sunday, February 16, 2003 8:00 PM
> Subject: RE: Request to Fix Tomcat Standalone 302 redirect Issue
>
>
>
>>So it *will* be in tomcat 5?
>>
>>My head is spinning...so confusing.
>>
>>How does one access o.a.t.u.http.mapper.Mapper? Is this something that
>
> will
>
>>be configurable via web.xml?
>>
>
>
> It will be in configurable in 'server.xml' (or, at least it will be when I
> do my next commit :).
Good, the code looks like as if I had written it myself :)
However, it poses the usual security problems, and breaks the admin webapp.
Remy
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
RE: Request to Fix Tomcat Standalone 302 redirect Issue
Posted by Jim Smart <ji...@jimsmart.org>.
Can this functionality be back-ported to the 4.1 tree?
tia,
Jim
> -----Original Message-----
> From: Bill Barker [mailto:wbarker@wilshire.com]
> Sent: 17 February 2003 04:48
> To: Tomcat Developers List
> Subject: Re: Request to Fix Tomcat Standalone 302 redirect Issue
>
>
>
> ----- Original Message -----
> From: "neal" <ne...@yahoo.com>
> To: "Tomcat Developers List" <to...@jakarta.apache.org>
> Sent: Sunday, February 16, 2003 8:00 PM
> Subject: RE: Request to Fix Tomcat Standalone 302 redirect Issue
>
>
> > So it *will* be in tomcat 5?
> >
> > My head is spinning...so confusing.
> >
> > How does one access o.a.t.u.http.mapper.Mapper? Is this something that
> will
> > be configurable via web.xml?
> >
>
> It will be in configurable in 'server.xml' (or, at least it will be when I
> do my next commit :).
>
> > Anyone have a ballpark idea on when Tomcat 5 will be released?
> Or at least
> > when a release-candidate-quality binary will be available?
> >
> > :)
> >
> > Thanks.
> > Neal
> >
> > -----Original Message-----
> > From: Bill Barker [mailto:wbarker@wilshire.com]
> > Sent: Sunday, February 16, 2003 8:01 PM
> > To: Tomcat Developers List
> > Subject: Re: Request to Fix Tomcat Standalone 302 redirect Issue
> >
> >
> > For TC 5, it isn't in DefaultServlet (which gets called way too late).
> It's
> > in o.a.t.u.http.mapper.Mapper.
> >
> > ----- Original Message -----
> > From: "Tim Funk" <fu...@joedog.org>
> > To: "Tomcat Developers List" <to...@jakarta.apache.org>
> > Sent: Sunday, February 16, 2003 6:43 PM
> > Subject: Re: Request to Fix Tomcat Standalone 302 redirect Issue
> >
> >
> > > If I remember that thread correctly, the functionality was not been
> > > added according to the code.
> > >
> > >
> >
> http://cvs.apache.org/viewcvs.cgi/jakarta-tomcat-catalina/catalina
> /src/share
> >
> /org/apache/catalina/servlets/DefaultServlet.java?rev=1.5&content-
> type=text/
> > vnd.viewcvs-markup
> > >
> > > -Tim
> > >
> > >
> > > neal wrote:
> > > > I just took a look at the web.xml file found within the tomcat 5
> > download
> > > > (jakarta-tomcat-catalina/catalina/conf) and saw no indication of the
> > > > inclusion of this patch.
> > > >
> > > > Per indications in the thread referred to below, I looked for an
> > indication
> > > > that an init parameter was included that could be toggled to achieve
> > this
> > > > behavior but nothing was denoted in the comments above this
> node that
> > would
> > > > suggest it is a new feature.
> > > >
> > > > Could someone please confirm that this feature has been
> included into
> > tomcat
> > > > 5 and instruct me as to how I would access this new
> functionality? I
> > really
> > > > really really want the forward behavior for my default page. :-\
> > > >
> > > >
> > > > Thanks
> > > > Neal
> > > >
> > > > -----Original Message-----
> > > > From: Tim Funk [mailto:funkman@joedog.org]
> > > > Sent: Sunday, February 16, 2003 11:39 AM
> > > > To: Tomcat Developers List
> > > > Subject: Re: Request to Fix Tomcat Standalone 302 redirect Issue
> > > >
> > > >
> > > > 5 will *probably* not be final until
> > > > - The specs(Serlvet 2.4, jsp 2.) become final
> > > > - The many internal changes are tested more
> > > > - The committers vote to declare it so
> > > >
> > > > From seeing past messages - it looks like the specs being declared
> > > > final is the buggest hurdle (to wait for). (But there have been some
> > > > significant internal changes which need more testing)
> > > >
> > > > But anyone is free to use it since the source is available to make
> their
> > > > own release.
> > > >
> > > > -Tim
> > > >
> > > > neal wrote:
> > > >
> > > >>Actually, I just went to download tomcat 5 and it looks like there's
> no
> > > >>release candidate of Tomcat 5 yet ... that its still in testing. Is
> > this
> > > >>correct? Does anyone know a timeframe for release?
> > > >>
> > > >>Thanks.
> > > >>Neal
> > > >>
> > > >
> > > >
> > > >
> > > >
> > > >
> ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
> > > > For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
> > > >
> > > >
> > > >
> ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
> > > > For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
> > > >
> > > >
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
> > > For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
> > >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
> >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
Re: Request to Fix Tomcat Standalone 302 redirect Issue
Posted by Bill Barker <wb...@wilshire.com>.
----- Original Message -----
From: "neal" <ne...@yahoo.com>
To: "Tomcat Developers List" <to...@jakarta.apache.org>
Sent: Sunday, February 16, 2003 8:00 PM
Subject: RE: Request to Fix Tomcat Standalone 302 redirect Issue
> So it *will* be in tomcat 5?
>
> My head is spinning...so confusing.
>
> How does one access o.a.t.u.http.mapper.Mapper? Is this something that
will
> be configurable via web.xml?
>
It will be in configurable in 'server.xml' (or, at least it will be when I
do my next commit :).
> Anyone have a ballpark idea on when Tomcat 5 will be released? Or at least
> when a release-candidate-quality binary will be available?
>
> :)
>
> Thanks.
> Neal
>
> -----Original Message-----
> From: Bill Barker [mailto:wbarker@wilshire.com]
> Sent: Sunday, February 16, 2003 8:01 PM
> To: Tomcat Developers List
> Subject: Re: Request to Fix Tomcat Standalone 302 redirect Issue
>
>
> For TC 5, it isn't in DefaultServlet (which gets called way too late).
It's
> in o.a.t.u.http.mapper.Mapper.
>
> ----- Original Message -----
> From: "Tim Funk" <fu...@joedog.org>
> To: "Tomcat Developers List" <to...@jakarta.apache.org>
> Sent: Sunday, February 16, 2003 6:43 PM
> Subject: Re: Request to Fix Tomcat Standalone 302 redirect Issue
>
>
> > If I remember that thread correctly, the functionality was not been
> > added according to the code.
> >
> >
>
http://cvs.apache.org/viewcvs.cgi/jakarta-tomcat-catalina/catalina/src/share
>
/org/apache/catalina/servlets/DefaultServlet.java?rev=1.5&content-type=text/
> vnd.viewcvs-markup
> >
> > -Tim
> >
> >
> > neal wrote:
> > > I just took a look at the web.xml file found within the tomcat 5
> download
> > > (jakarta-tomcat-catalina/catalina/conf) and saw no indication of the
> > > inclusion of this patch.
> > >
> > > Per indications in the thread referred to below, I looked for an
> indication
> > > that an init parameter was included that could be toggled to achieve
> this
> > > behavior but nothing was denoted in the comments above this node that
> would
> > > suggest it is a new feature.
> > >
> > > Could someone please confirm that this feature has been included into
> tomcat
> > > 5 and instruct me as to how I would access this new functionality? I
> really
> > > really really want the forward behavior for my default page. :-\
> > >
> > >
> > > Thanks
> > > Neal
> > >
> > > -----Original Message-----
> > > From: Tim Funk [mailto:funkman@joedog.org]
> > > Sent: Sunday, February 16, 2003 11:39 AM
> > > To: Tomcat Developers List
> > > Subject: Re: Request to Fix Tomcat Standalone 302 redirect Issue
> > >
> > >
> > > 5 will *probably* not be final until
> > > - The specs(Serlvet 2.4, jsp 2.) become final
> > > - The many internal changes are tested more
> > > - The committers vote to declare it so
> > >
> > > From seeing past messages - it looks like the specs being declared
> > > final is the buggest hurdle (to wait for). (But there have been some
> > > significant internal changes which need more testing)
> > >
> > > But anyone is free to use it since the source is available to make
their
> > > own release.
> > >
> > > -Tim
> > >
> > > neal wrote:
> > >
> > >>Actually, I just went to download tomcat 5 and it looks like there's
no
> > >>release candidate of Tomcat 5 yet ... that its still in testing. Is
> this
> > >>correct? Does anyone know a timeframe for release?
> > >>
> > >>Thanks.
> > >>Neal
> > >>
> > >
> > >
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
> > > For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
> > > For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
> > >
> > >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
RE: Request to Fix Tomcat Standalone 302 redirect Issue
Posted by neal <ne...@yahoo.com>.
So it *will* be in tomcat 5?
My head is spinning...so confusing.
How does one access o.a.t.u.http.mapper.Mapper? Is this something that will
be configurable via web.xml?
Anyone have a ballpark idea on when Tomcat 5 will be released? Or at least
when a release-candidate-quality binary will be available?
:)
Thanks.
Neal
-----Original Message-----
From: Bill Barker [mailto:wbarker@wilshire.com]
Sent: Sunday, February 16, 2003 8:01 PM
To: Tomcat Developers List
Subject: Re: Request to Fix Tomcat Standalone 302 redirect Issue
For TC 5, it isn't in DefaultServlet (which gets called way too late). It's
in o.a.t.u.http.mapper.Mapper.
----- Original Message -----
From: "Tim Funk" <fu...@joedog.org>
To: "Tomcat Developers List" <to...@jakarta.apache.org>
Sent: Sunday, February 16, 2003 6:43 PM
Subject: Re: Request to Fix Tomcat Standalone 302 redirect Issue
> If I remember that thread correctly, the functionality was not been
> added according to the code.
>
>
http://cvs.apache.org/viewcvs.cgi/jakarta-tomcat-catalina/catalina/src/share
/org/apache/catalina/servlets/DefaultServlet.java?rev=1.5&content-type=text/
vnd.viewcvs-markup
>
> -Tim
>
>
> neal wrote:
> > I just took a look at the web.xml file found within the tomcat 5
download
> > (jakarta-tomcat-catalina/catalina/conf) and saw no indication of the
> > inclusion of this patch.
> >
> > Per indications in the thread referred to below, I looked for an
indication
> > that an init parameter was included that could be toggled to achieve
this
> > behavior but nothing was denoted in the comments above this node that
would
> > suggest it is a new feature.
> >
> > Could someone please confirm that this feature has been included into
tomcat
> > 5 and instruct me as to how I would access this new functionality? I
really
> > really really want the forward behavior for my default page. :-\
> >
> >
> > Thanks
> > Neal
> >
> > -----Original Message-----
> > From: Tim Funk [mailto:funkman@joedog.org]
> > Sent: Sunday, February 16, 2003 11:39 AM
> > To: Tomcat Developers List
> > Subject: Re: Request to Fix Tomcat Standalone 302 redirect Issue
> >
> >
> > 5 will *probably* not be final until
> > - The specs(Serlvet 2.4, jsp 2.) become final
> > - The many internal changes are tested more
> > - The committers vote to declare it so
> >
> > From seeing past messages - it looks like the specs being declared
> > final is the buggest hurdle (to wait for). (But there have been some
> > significant internal changes which need more testing)
> >
> > But anyone is free to use it since the source is available to make their
> > own release.
> >
> > -Tim
> >
> > neal wrote:
> >
> >>Actually, I just went to download tomcat 5 and it looks like there's no
> >>release candidate of Tomcat 5 yet ... that its still in testing. Is
this
> >>correct? Does anyone know a timeframe for release?
> >>
> >>Thanks.
> >>Neal
> >>
> >
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
> >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
Re: Request to Fix Tomcat Standalone 302 redirect Issue
Posted by Bill Barker <wb...@wilshire.com>.
For TC 5, it isn't in DefaultServlet (which gets called way too late). It's
in o.a.t.u.http.mapper.Mapper.
----- Original Message -----
From: "Tim Funk" <fu...@joedog.org>
To: "Tomcat Developers List" <to...@jakarta.apache.org>
Sent: Sunday, February 16, 2003 6:43 PM
Subject: Re: Request to Fix Tomcat Standalone 302 redirect Issue
> If I remember that thread correctly, the functionality was not been
> added according to the code.
>
>
http://cvs.apache.org/viewcvs.cgi/jakarta-tomcat-catalina/catalina/src/share
/org/apache/catalina/servlets/DefaultServlet.java?rev=1.5&content-type=text/
vnd.viewcvs-markup
>
> -Tim
>
>
> neal wrote:
> > I just took a look at the web.xml file found within the tomcat 5
download
> > (jakarta-tomcat-catalina/catalina/conf) and saw no indication of the
> > inclusion of this patch.
> >
> > Per indications in the thread referred to below, I looked for an
indication
> > that an init parameter was included that could be toggled to achieve
this
> > behavior but nothing was denoted in the comments above this node that
would
> > suggest it is a new feature.
> >
> > Could someone please confirm that this feature has been included into
tomcat
> > 5 and instruct me as to how I would access this new functionality? I
really
> > really really want the forward behavior for my default page. :-\
> >
> >
> > Thanks
> > Neal
> >
> > -----Original Message-----
> > From: Tim Funk [mailto:funkman@joedog.org]
> > Sent: Sunday, February 16, 2003 11:39 AM
> > To: Tomcat Developers List
> > Subject: Re: Request to Fix Tomcat Standalone 302 redirect Issue
> >
> >
> > 5 will *probably* not be final until
> > - The specs(Serlvet 2.4, jsp 2.) become final
> > - The many internal changes are tested more
> > - The committers vote to declare it so
> >
> > From seeing past messages - it looks like the specs being declared
> > final is the buggest hurdle (to wait for). (But there have been some
> > significant internal changes which need more testing)
> >
> > But anyone is free to use it since the source is available to make their
> > own release.
> >
> > -Tim
> >
> > neal wrote:
> >
> >>Actually, I just went to download tomcat 5 and it looks like there's no
> >>release candidate of Tomcat 5 yet ... that its still in testing. Is
this
> >>correct? Does anyone know a timeframe for release?
> >>
> >>Thanks.
> >>Neal
> >>
> >
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
> >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
RE: Request to Fix Tomcat Standalone 302 redirect Issue
Posted by neal <ne...@yahoo.com>.
Seriously?!?! Why does this effort keep getting blocked?!?!?
This is a huge Search engine issue. For crying out loud .. Search engines
SLAM sites that use redirects, particularly on the main page!!!
If its not going to be fixed, Apache should seriously consider saving other
developers the grief I've been going through by either (a) scrapping the
standlone notion altogether so as not to confuse or (b) puttin a HUGE red
dislclaimer on the download page that says "the product is not commercially
viable".
Could someone please confirm for me if this will be fixed in a near-term
future release? If not, I guess I need to completely scrap use of Tomcat
standalone and start looking at other products. :-\
Thanks.
Neal
-----Original Message-----
From: Tim Funk [mailto:funkman@joedog.org]
Sent: Sunday, February 16, 2003 6:44 PM
To: Tomcat Developers List
Subject: Re: Request to Fix Tomcat Standalone 302 redirect Issue
If I remember that thread correctly, the functionality was not been
added according to the code.
http://cvs.apache.org/viewcvs.cgi/jakarta-tomcat-catalina/catalina/src/share
/org/apache/catalina/servlets/DefaultServlet.java?rev=1.5&content-type=text/
vnd.viewcvs-markup
-Tim
neal wrote:
> I just took a look at the web.xml file found within the tomcat 5 download
> (jakarta-tomcat-catalina/catalina/conf) and saw no indication of the
> inclusion of this patch.
>
> Per indications in the thread referred to below, I looked for an
indication
> that an init parameter was included that could be toggled to achieve this
> behavior but nothing was denoted in the comments above this node that
would
> suggest it is a new feature.
>
> Could someone please confirm that this feature has been included into
tomcat
> 5 and instruct me as to how I would access this new functionality? I
really
> really really want the forward behavior for my default page. :-\
>
>
> Thanks
> Neal
>
> -----Original Message-----
> From: Tim Funk [mailto:funkman@joedog.org]
> Sent: Sunday, February 16, 2003 11:39 AM
> To: Tomcat Developers List
> Subject: Re: Request to Fix Tomcat Standalone 302 redirect Issue
>
>
> 5 will *probably* not be final until
> - The specs(Serlvet 2.4, jsp 2.) become final
> - The many internal changes are tested more
> - The committers vote to declare it so
>
> From seeing past messages - it looks like the specs being declared
> final is the buggest hurdle (to wait for). (But there have been some
> significant internal changes which need more testing)
>
> But anyone is free to use it since the source is available to make their
> own release.
>
> -Tim
>
> neal wrote:
>
>>Actually, I just went to download tomcat 5 and it looks like there's no
>>release candidate of Tomcat 5 yet ... that its still in testing. Is this
>>correct? Does anyone know a timeframe for release?
>>
>>Thanks.
>>Neal
>>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
Re: Request to Fix Tomcat Standalone 302 redirect Issue
Posted by Tim Funk <fu...@joedog.org>.
If I remember that thread correctly, the functionality was not been
added according to the code.
http://cvs.apache.org/viewcvs.cgi/jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/servlets/DefaultServlet.java?rev=1.5&content-type=text/vnd.viewcvs-markup
-Tim
neal wrote:
> I just took a look at the web.xml file found within the tomcat 5 download
> (jakarta-tomcat-catalina/catalina/conf) and saw no indication of the
> inclusion of this patch.
>
> Per indications in the thread referred to below, I looked for an indication
> that an init parameter was included that could be toggled to achieve this
> behavior but nothing was denoted in the comments above this node that would
> suggest it is a new feature.
>
> Could someone please confirm that this feature has been included into tomcat
> 5 and instruct me as to how I would access this new functionality? I really
> really really want the forward behavior for my default page. :-\
>
>
> Thanks
> Neal
>
> -----Original Message-----
> From: Tim Funk [mailto:funkman@joedog.org]
> Sent: Sunday, February 16, 2003 11:39 AM
> To: Tomcat Developers List
> Subject: Re: Request to Fix Tomcat Standalone 302 redirect Issue
>
>
> 5 will *probably* not be final until
> - The specs(Serlvet 2.4, jsp 2.) become final
> - The many internal changes are tested more
> - The committers vote to declare it so
>
> From seeing past messages - it looks like the specs being declared
> final is the buggest hurdle (to wait for). (But there have been some
> significant internal changes which need more testing)
>
> But anyone is free to use it since the source is available to make their
> own release.
>
> -Tim
>
> neal wrote:
>
>>Actually, I just went to download tomcat 5 and it looks like there's no
>>release candidate of Tomcat 5 yet ... that its still in testing. Is this
>>correct? Does anyone know a timeframe for release?
>>
>>Thanks.
>>Neal
>>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
RE: Request to Fix Tomcat Standalone 302 redirect Issue
Posted by neal <ne...@yahoo.com>.
I just took a look at the web.xml file found within the tomcat 5 download
(jakarta-tomcat-catalina/catalina/conf) and saw no indication of the
inclusion of this patch.
Per indications in the thread referred to below, I looked for an indication
that an init parameter was included that could be toggled to achieve this
behavior but nothing was denoted in the comments above this node that would
suggest it is a new feature.
Could someone please confirm that this feature has been included into tomcat
5 and instruct me as to how I would access this new functionality? I really
really really want the forward behavior for my default page. :-\
Thanks
Neal
-----Original Message-----
From: Tim Funk [mailto:funkman@joedog.org]
Sent: Sunday, February 16, 2003 11:39 AM
To: Tomcat Developers List
Subject: Re: Request to Fix Tomcat Standalone 302 redirect Issue
5 will *probably* not be final until
- The specs(Serlvet 2.4, jsp 2.) become final
- The many internal changes are tested more
- The committers vote to declare it so
From seeing past messages - it looks like the specs being declared
final is the buggest hurdle (to wait for). (But there have been some
significant internal changes which need more testing)
But anyone is free to use it since the source is available to make their
own release.
-Tim
neal wrote:
> Actually, I just went to download tomcat 5 and it looks like there's no
> release candidate of Tomcat 5 yet ... that its still in testing. Is this
> correct? Does anyone know a timeframe for release?
>
> Thanks.
> Neal
>
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
Re: Request to Fix Tomcat Standalone 302 redirect Issue
Posted by Tim Funk <fu...@joedog.org>.
5 will *probably* not be final until
- The specs(Serlvet 2.4, jsp 2.) become final
- The many internal changes are tested more
- The committers vote to declare it so
From seeing past messages - it looks like the specs being declared
final is the buggest hurdle (to wait for). (But there have been some
significant internal changes which need more testing)
But anyone is free to use it since the source is available to make their
own release.
-Tim
neal wrote:
> Actually, I just went to download tomcat 5 and it looks like there's no
> release candidate of Tomcat 5 yet ... that its still in testing. Is this
> correct? Does anyone know a timeframe for release?
>
> Thanks.
> Neal
>
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
RE: Request to Fix Tomcat Standalone 302 redirect Issue
Posted by neal <ne...@yahoo.com>.
Actually, I just went to download tomcat 5 and it looks like there's no
release candidate of Tomcat 5 yet ... that its still in testing. Is this
correct? Does anyone know a timeframe for release?
Thanks.
Neal
-----Original Message-----
From: neal [mailto:nealcabage@yahoo.com]
Sent: Sunday, February 16, 2003 11:12 AM
To: Tomcat Developers List
Subject: RE: Request to Fix Tomcat Standalone 302 redirect Issue
Actually, I found the archives by doing a google web search.
In the thread it *sounds* like it has been added to Tomcat 5.0 and is not
something I can toggle within the web.xml file. Is there any documentation
on this? What precisely do I change within the web.xml file to get this
behavior?
In the meantime I suppose I'll download tomcat 5.0 and play around to see if
its something I can figure out.
Thanks
Neal
-----Original Message-----
From: neal [mailto:nealcabage@yahoo.com]
Sent: Sunday, February 16, 2003 10:58 AM
To: Tomcat Developers List
Subject: RE: Request to Fix Tomcat Standalone 302 redirect Issue
Actually,
How can I check the archives of this list? I did a search for the thread on
google groups and nothing was found. I looked for the archives on
apache.org but it looks like archives haven't been kept since then end of
2001. :(
Thanks
Neal
-----Original Message-----
From: neal [mailto:nealcabage@yahoo.com]
Sent: Sunday, February 16, 2003 10:54 AM
To: Tomcat Developers List
Subject: RE: Request to Fix Tomcat Standalone 302 redirect Issue
Aha! That's exactly what I was looking for - a forward rather than a
redirect! Great, I will check out the thread and keep my fingers crossed
that this is an optional behavior in Tomcat 5.
As for the status, might I suggest that so long as this behavior is not
changed and not optional that it should be well documented. This can be a
serious caveat ... and a quite unexpected one. The documentation for Tomcat
standalone gives no indication that it is inferior or that it implements an
alternative standard due to the existance of apache. But if that's the case
it should be noted as a guide for people new to the product who need to make
informed decisions.
Thanks.
Neal
-----Original Message-----
From: Reinhard Moosauer [mailto:rm@moosauer.de]
Sent: Sunday, February 16, 2003 4:47 AM
To: Tomcat Developers List
Subject: Re: Request to Fix Tomcat Standalone 302 redirect Issue
Hi,
at Jan 03, 2003 Matt Parker published a patch in this list:
"[PATCH] forward instead of redirect for welcome files"
which was discussed thourougly with Costin, Remy and others.
I'm not sure about the conclusion of this. But it seemed that 5.0 should
reintroduce this behavior by option.
Please read that thread. Maybe there are some hints to get further.
(I am also very interested in this changing this, but as long as apache ist
an
option, the priority stays medium...)
Kind regards,
Reinhard
Am Sonntag, 16. Februar 2003 00:41 schrieb neal:
> Has anyone considered fixing the following Tomcat standalone issue:
>
> if a request is made to "www.xyz.com", tomcat auto redirects (per the
> welcome files list) to "www.xyz.com/index.html". That's a 302 http
> redirect. Aside from this being a very non-standard approach th handling
> default files within a directory, it is extremely problematic when dealing
> with Search Engines.
>
> Search engines hate 302s and penalize most sites that utilize them,
> particularly as their default page. Further in the case of Google, a page
> rank is assigned to a url based upon inboind links. If the inboind links
> are all to "www.xyz.com" and that url is just a redirect, you will never
> benefit from the inbound links to your default url and never achieve a
nigh
> ranking.
>
> For these reasons this "feature" of tomcat renders the standalone http
> server virtually commercially non-viable. This is a major concern for any
> commercial site that reaps traffic from search engines, or from inbound
> links.
>
> I setup my site using tomcat standalone because I saw no reason to set it
> up with Apache initially. But this one single reason is making me
> seriously second guess that choice. Is this not somehting that can be
> easily fixed in a future version? And if it can be fixed .... I would
> like to beg ... grovel ... anything ... to have this changed. Otherwise,
> re-setting up with apache is going to cost me a fair amount of $$$ and
time
> at this point. :-\
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
RE: Request to Fix Tomcat Standalone 302 redirect Issue
Posted by neal <ne...@yahoo.com>.
Actually, I found the archives by doing a google web search.
In the thread it *sounds* like it has been added to Tomcat 5.0 and is not
something I can toggle within the web.xml file. Is there any documentation
on this? What precisely do I change within the web.xml file to get this
behavior?
In the meantime I suppose I'll download tomcat 5.0 and play around to see if
its something I can figure out.
Thanks
Neal
-----Original Message-----
From: neal [mailto:nealcabage@yahoo.com]
Sent: Sunday, February 16, 2003 10:58 AM
To: Tomcat Developers List
Subject: RE: Request to Fix Tomcat Standalone 302 redirect Issue
Actually,
How can I check the archives of this list? I did a search for the thread on
google groups and nothing was found. I looked for the archives on
apache.org but it looks like archives haven't been kept since then end of
2001. :(
Thanks
Neal
-----Original Message-----
From: neal [mailto:nealcabage@yahoo.com]
Sent: Sunday, February 16, 2003 10:54 AM
To: Tomcat Developers List
Subject: RE: Request to Fix Tomcat Standalone 302 redirect Issue
Aha! That's exactly what I was looking for - a forward rather than a
redirect! Great, I will check out the thread and keep my fingers crossed
that this is an optional behavior in Tomcat 5.
As for the status, might I suggest that so long as this behavior is not
changed and not optional that it should be well documented. This can be a
serious caveat ... and a quite unexpected one. The documentation for Tomcat
standalone gives no indication that it is inferior or that it implements an
alternative standard due to the existance of apache. But if that's the case
it should be noted as a guide for people new to the product who need to make
informed decisions.
Thanks.
Neal
-----Original Message-----
From: Reinhard Moosauer [mailto:rm@moosauer.de]
Sent: Sunday, February 16, 2003 4:47 AM
To: Tomcat Developers List
Subject: Re: Request to Fix Tomcat Standalone 302 redirect Issue
Hi,
at Jan 03, 2003 Matt Parker published a patch in this list:
"[PATCH] forward instead of redirect for welcome files"
which was discussed thourougly with Costin, Remy and others.
I'm not sure about the conclusion of this. But it seemed that 5.0 should
reintroduce this behavior by option.
Please read that thread. Maybe there are some hints to get further.
(I am also very interested in this changing this, but as long as apache ist
an
option, the priority stays medium...)
Kind regards,
Reinhard
Am Sonntag, 16. Februar 2003 00:41 schrieb neal:
> Has anyone considered fixing the following Tomcat standalone issue:
>
> if a request is made to "www.xyz.com", tomcat auto redirects (per the
> welcome files list) to "www.xyz.com/index.html". That's a 302 http
> redirect. Aside from this being a very non-standard approach th handling
> default files within a directory, it is extremely problematic when dealing
> with Search Engines.
>
> Search engines hate 302s and penalize most sites that utilize them,
> particularly as their default page. Further in the case of Google, a page
> rank is assigned to a url based upon inboind links. If the inboind links
> are all to "www.xyz.com" and that url is just a redirect, you will never
> benefit from the inbound links to your default url and never achieve a
nigh
> ranking.
>
> For these reasons this "feature" of tomcat renders the standalone http
> server virtually commercially non-viable. This is a major concern for any
> commercial site that reaps traffic from search engines, or from inbound
> links.
>
> I setup my site using tomcat standalone because I saw no reason to set it
> up with Apache initially. But this one single reason is making me
> seriously second guess that choice. Is this not somehting that can be
> easily fixed in a future version? And if it can be fixed .... I would
> like to beg ... grovel ... anything ... to have this changed. Otherwise,
> re-setting up with apache is going to cost me a fair amount of $$$ and
time
> at this point. :-\
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
RE: Request to Fix Tomcat Standalone 302 redirect Issue
Posted by neal <ne...@yahoo.com>.
Actually,
How can I check the archives of this list? I did a search for the thread on
google groups and nothing was found. I looked for the archives on
apache.org but it looks like archives haven't been kept since then end of
2001. :(
Thanks
Neal
-----Original Message-----
From: neal [mailto:nealcabage@yahoo.com]
Sent: Sunday, February 16, 2003 10:54 AM
To: Tomcat Developers List
Subject: RE: Request to Fix Tomcat Standalone 302 redirect Issue
Aha! That's exactly what I was looking for - a forward rather than a
redirect! Great, I will check out the thread and keep my fingers crossed
that this is an optional behavior in Tomcat 5.
As for the status, might I suggest that so long as this behavior is not
changed and not optional that it should be well documented. This can be a
serious caveat ... and a quite unexpected one. The documentation for Tomcat
standalone gives no indication that it is inferior or that it implements an
alternative standard due to the existance of apache. But if that's the case
it should be noted as a guide for people new to the product who need to make
informed decisions.
Thanks.
Neal
-----Original Message-----
From: Reinhard Moosauer [mailto:rm@moosauer.de]
Sent: Sunday, February 16, 2003 4:47 AM
To: Tomcat Developers List
Subject: Re: Request to Fix Tomcat Standalone 302 redirect Issue
Hi,
at Jan 03, 2003 Matt Parker published a patch in this list:
"[PATCH] forward instead of redirect for welcome files"
which was discussed thourougly with Costin, Remy and others.
I'm not sure about the conclusion of this. But it seemed that 5.0 should
reintroduce this behavior by option.
Please read that thread. Maybe there are some hints to get further.
(I am also very interested in this changing this, but as long as apache ist
an
option, the priority stays medium...)
Kind regards,
Reinhard
Am Sonntag, 16. Februar 2003 00:41 schrieb neal:
> Has anyone considered fixing the following Tomcat standalone issue:
>
> if a request is made to "www.xyz.com", tomcat auto redirects (per the
> welcome files list) to "www.xyz.com/index.html". That's a 302 http
> redirect. Aside from this being a very non-standard approach th handling
> default files within a directory, it is extremely problematic when dealing
> with Search Engines.
>
> Search engines hate 302s and penalize most sites that utilize them,
> particularly as their default page. Further in the case of Google, a page
> rank is assigned to a url based upon inboind links. If the inboind links
> are all to "www.xyz.com" and that url is just a redirect, you will never
> benefit from the inbound links to your default url and never achieve a
nigh
> ranking.
>
> For these reasons this "feature" of tomcat renders the standalone http
> server virtually commercially non-viable. This is a major concern for any
> commercial site that reaps traffic from search engines, or from inbound
> links.
>
> I setup my site using tomcat standalone because I saw no reason to set it
> up with Apache initially. But this one single reason is making me
> seriously second guess that choice. Is this not somehting that can be
> easily fixed in a future version? And if it can be fixed .... I would
> like to beg ... grovel ... anything ... to have this changed. Otherwise,
> re-setting up with apache is going to cost me a fair amount of $$$ and
time
> at this point. :-\
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
RE: Request to Fix Tomcat Standalone 302 redirect Issue
Posted by neal <ne...@yahoo.com>.
Aha! That's exactly what I was looking for - a forward rather than a
redirect! Great, I will check out the thread and keep my fingers crossed
that this is an optional behavior in Tomcat 5.
As for the status, might I suggest that so long as this behavior is not
changed and not optional that it should be well documented. This can be a
serious caveat ... and a quite unexpected one. The documentation for Tomcat
standalone gives no indication that it is inferior or that it implements an
alternative standard due to the existance of apache. But if that's the case
it should be noted as a guide for people new to the product who need to make
informed decisions.
Thanks.
Neal
-----Original Message-----
From: Reinhard Moosauer [mailto:rm@moosauer.de]
Sent: Sunday, February 16, 2003 4:47 AM
To: Tomcat Developers List
Subject: Re: Request to Fix Tomcat Standalone 302 redirect Issue
Hi,
at Jan 03, 2003 Matt Parker published a patch in this list:
"[PATCH] forward instead of redirect for welcome files"
which was discussed thourougly with Costin, Remy and others.
I'm not sure about the conclusion of this. But it seemed that 5.0 should
reintroduce this behavior by option.
Please read that thread. Maybe there are some hints to get further.
(I am also very interested in this changing this, but as long as apache ist
an
option, the priority stays medium...)
Kind regards,
Reinhard
Am Sonntag, 16. Februar 2003 00:41 schrieb neal:
> Has anyone considered fixing the following Tomcat standalone issue:
>
> if a request is made to "www.xyz.com", tomcat auto redirects (per the
> welcome files list) to "www.xyz.com/index.html". That's a 302 http
> redirect. Aside from this being a very non-standard approach th handling
> default files within a directory, it is extremely problematic when dealing
> with Search Engines.
>
> Search engines hate 302s and penalize most sites that utilize them,
> particularly as their default page. Further in the case of Google, a page
> rank is assigned to a url based upon inboind links. If the inboind links
> are all to "www.xyz.com" and that url is just a redirect, you will never
> benefit from the inbound links to your default url and never achieve a
nigh
> ranking.
>
> For these reasons this "feature" of tomcat renders the standalone http
> server virtually commercially non-viable. This is a major concern for any
> commercial site that reaps traffic from search engines, or from inbound
> links.
>
> I setup my site using tomcat standalone because I saw no reason to set it
> up with Apache initially. But this one single reason is making me
> seriously second guess that choice. Is this not somehting that can be
> easily fixed in a future version? And if it can be fixed .... I would
> like to beg ... grovel ... anything ... to have this changed. Otherwise,
> re-setting up with apache is going to cost me a fair amount of $$$ and
time
> at this point. :-\
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
Re: Request to Fix Tomcat Standalone 302 redirect Issue
Posted by Reinhard Moosauer <rm...@moosauer.de>.
Hi,
at Jan 03, 2003 Matt Parker published a patch in this list:
"[PATCH] forward instead of redirect for welcome files"
which was discussed thourougly with Costin, Remy and others.
I'm not sure about the conclusion of this. But it seemed that 5.0 should
reintroduce this behavior by option.
Please read that thread. Maybe there are some hints to get further.
(I am also very interested in this changing this, but as long as apache ist an
option, the priority stays medium...)
Kind regards,
Reinhard
Am Sonntag, 16. Februar 2003 00:41 schrieb neal:
> Has anyone considered fixing the following Tomcat standalone issue:
>
> if a request is made to "www.xyz.com", tomcat auto redirects (per the
> welcome files list) to "www.xyz.com/index.html". That's a 302 http
> redirect. Aside from this being a very non-standard approach th handling
> default files within a directory, it is extremely problematic when dealing
> with Search Engines.
>
> Search engines hate 302s and penalize most sites that utilize them,
> particularly as their default page. Further in the case of Google, a page
> rank is assigned to a url based upon inboind links. If the inboind links
> are all to "www.xyz.com" and that url is just a redirect, you will never
> benefit from the inbound links to your default url and never achieve a nigh
> ranking.
>
> For these reasons this "feature" of tomcat renders the standalone http
> server virtually commercially non-viable. This is a major concern for any
> commercial site that reaps traffic from search engines, or from inbound
> links.
>
> I setup my site using tomcat standalone because I saw no reason to set it
> up with Apache initially. But this one single reason is making me
> seriously second guess that choice. Is this not somehting that can be
> easily fixed in a future version? And if it can be fixed .... I would
> like to beg ... grovel ... anything ... to have this changed. Otherwise,
> re-setting up with apache is going to cost me a fair amount of $$$ and time
> at this point. :-\
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org