tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Siddhartha Subramanian" <siddhartha.subraman...@nortel.com>
Subject RE: sendRedirect scheme
Date Fri, 29 Dec 2006 22:11:52 GMT
well for those who are not in favor of email dump sorry.. here are the file contents..

---

<Server>

      <!-- Use a custom version of StandardService that allows the

   connectors to be started independent of the normal lifecycle

   start to allow web apps to be deployed before starting the

   connectors.

   -->

      <Service name="jboss.web" className="org.jboss.web.tomcat.tc5.StandardService">

            <!-- A HTTP/1.1 Connector on port 8080 -->

            <!--Connector port="8080" address="${jboss.bind.address}" maxThreads="250"
strategy="ms" maxHttpHeaderSize="8192" emptySessionPath="true" redirectPort="8443" enableLookups="false"
acceptCount="100" connectionTimeout="20000" disableUploadTimeout="true"/-->

            <Connector port="80" address="${jboss.bind.address}" maxThreads="250" strategy="ms"
maxHttpHeaderSize="8192" emptySessionPath="true" enableLookups="false" acceptCount="100" connectionTimeout="20000"
disableUploadTimeout="true" protocol="HTTP/1.1" scheme="http"/>

            <!-- Add this option to the connector to avoid problems with 

          .NET clients that don't implement HTTP/1.1 correctly 

         restrictedUserAgents="^.*MS Web Services Client Protocol 1.1.4322.*$"

      -->

            <!-- A AJP 1.3 Connector on port 8009 -->

            <!--Connector port="8009" address="${jboss.bind.address}" emptySessionPath="true"
enableLookups="false" redirectPort="8443" protocol="AJP/1.3"/-->

            <!--SSL/TLS Connector configuration using the admin devl guide keystore

      <Connector port="8443" address="${jboss.bind.address}"

           maxThreads="100" strategy="ms" maxHttpHeaderSize="8192"

           emptySessionPath="true"

           scheme="https" secure="true" clientAuth="false" 

           keystoreFile="${jboss.server.home.dir}/conf/chap8.keystore"

           keystorePass="rmi+ssl" sslProtocol = "TLS" />

           

          -->

            <Engine name="jboss.web" defaultHost="localhost">

                  <!-- The JAAS based authentication and authorization realm implementation

         that is compatible with the jboss 3.2.x realm implementation.

         - certificatePrincipal : the class name of the

         org.jboss.security.auth.certs.CertificatePrincipal impl

         used for mapping X509[] cert chains to a Princpal.

         - allRolesMode : how to handle an auth-constraint with a role-name=*,

         one of strict, authOnly, strictAuthOnly

           + strict = Use the strict servlet spec interpretation which requires

           that the user have one of the web-app/security-role/role-name

           + authOnly = Allow any authenticated user

           + strictAuthOnly = Allow any authenticated user only if there are no

           web-app/security-roles

         -->

                  <Realm className="org.jboss.web.tomcat.security.JBossSecurityMgrRealm"
certificatePrincipal="org.jboss.security.auth.certs.SubjectDNMapping" allRolesMode="authOnly"/>

                  <!-- A subclass of JBossSecurityMgrRealm that uses the authentication

         behavior of JBossSecurityMgrRealm, but overrides the authorization

         checks to use JACC permissions with the current java.security.Policy

         to determine authorized access.

         - allRolesMode : how to handle an auth-constraint with a role-name=*,

         one of strict, authOnly, strictAuthOnly

           + strict = Use the strict servlet spec interpretation which requires

           that the user have one of the web-app/security-role/role-name

           + authOnly = Allow any authenticated user

           + strictAuthOnly = Allow any authenticated user only if there are no

           web-app/security-roles

         <Realm className="org.jboss.web.tomcat.security.JaccAuthorizationRealm"

            certificatePrincipal="org.jboss.security.auth.certs.SubjectDNMapping"

            allRolesMode="authOnly"

            />

         -->

                  <Host name="localhost" autoDeploy="false" deployOnStartup="false" deployXML="false"
configClass="org.jboss.web.tomcat.security.config.JBossContextConfig">

                        <!-- Uncomment to enable request dumper. This Valve "logs interesting


                 contents from the specified Request (before processing) and the 

                 corresponding Response (after processing). It is especially useful 

                 in debugging problems related to headers and cookies."

            -->

                        <!--

            <Valve className="org.apache.catalina.valves.RequestDumperValve" />

            -->

                        <!-- Access logger -->

                        <!--

            <Valve className="org.apache.catalina.valves.FastCommonAccessLogValve"

                prefix="localhost_access_log." suffix=".log"

                pattern="common" directory="${jboss.server.home.dir}/log" 

                resolveHosts="false" />

            -->

                        <!-- Uncomment to enable single sign-on across web apps

                deployed to this host. Does not provide SSO across a cluster.     

            

                If this valve is used, do not use the JBoss ClusteredSingleSignOn 

                valve shown below. 

                

                A new configuration attribute is available beginning with

                release 4.0.4:

                

                cookieDomain  configures the domain to which the SSO cookie

                              will be scoped (i.e. the set of hosts to

                              which the cookie will be presented).  By default

                              the cookie is scoped to "/", meaning the host

                              that presented it.  Set cookieDomain to a

                              wider domain (e.g. "xyz.com") to allow an SSO

                              to span more than one hostname.

             -->

                        <!--

            <Valve className="org.apache.catalina.authenticator.SingleSignOn" />

            -->

                        <!-- Uncomment to enable single sign-on across web apps

               deployed to this host AND to all other hosts in the cluster.

            

               If this valve is used, do not use the standard Tomcat SingleSignOn

               valve shown above.

            

               Valve uses a JBossCache instance to support SSO credential 

               caching and replication across the cluster.  The JBossCache 

               instance must be configured separately.  By default, the valve 

               shares a JBossCache with the service that supports HttpSession 

               replication.  See the "tc5-cluster-service.xml" file in the 

               server/all/deploy directory for cache configuration details.

            

               Besides the attributes supported by the standard Tomcat

               SingleSignOn valve (see the Tomcat docs), this version also 

               supports the following attributes:

            

               cookieDomain   see above

            

               treeCacheName  JMX ObjectName of the JBossCache MBean used to 

                              support credential caching and replication across

                              the cluster. If not set, the default value is 

                              "jboss.cache:service=TomcatClusteringCache", the 

                              standard ObjectName of the JBossCache MBean used 

                              to support session replication.

            -->

                        <!--

            <Valve className="org.jboss.web.tomcat.tc5.sso.ClusteredSingleSignOn" />

            -->

                        <!-- Check for unclosed connections and transaction terminated
checks

                 in servlets/jsps.

                 

                 Important: The dependency on the CachedConnectionManager

                 in META-INF/jboss-service.xml must be uncommented, too

            -->

                        <Valve className="org.jboss.web.tomcat.tc5.jca.CachedConnectionValve"
cachedConnectionManagerObjectName="jboss.jca:service=CachedConnectionManager" transactionManagerObjectName="jboss:service=TransactionManager"/>

                  </Host>

            </Engine>

      </Service>

</Server>

 

-----Original Message-----
From: Martin Gainty [mailto:mgainty@hotmail.com] 
Sent: Friday, December 29, 2006 4:06 PM
To: Tomcat Users List
Subject: Re: sendRedirect scheme

 

In one of those exceedingly rare moments where I agree with the previous poster can you cut
and paste your entire server.xml into the message body?

Also which browser version are you testing with?

 

Thx,

--------------------------------------------------------------------------- 

This e-mail message (including attachments, if any) is intended for the use of the individual
or entity to which it is addressed and may contain information that is privileged, proprietary
, confidential and exempt from disclosure. If you are not the intended recipient, you are
notified that any dissemination, distribution or copying of this communication is strictly
prohibited.

--------------------------------------------------------------------------- 

Le présent message électronique (y compris les pièces qui y sont annexées, le cas échéant)
s'adresse au destinataire indiqué et peut contenir des renseignements de caractère privé
ou confidentiel. Si vous n'êtes pas le destinataire de ce document, nous vous signalons qu'il
est strictement interdit de le diffuser, de le distribuer ou de le reproduire.

----- Original Message ----- 

From: "Caldarale, Charles R" <Chuck.Caldarale@unisys.com>

To: "Tomcat Users List" <users@tomcat.apache.org>

Sent: Friday, December 29, 2006 4:36 PM

Subject: RE: sendRedirect scheme

 

 

> From: Siddhartha Subramanian 

> [mailto:siddhartha.subramanian@nortel.com] 

> Subject: RE: sendRedirect scheme

> 

> Thanks for the information, I have tried all the possible 

> combinations 

> 

> <connector port="80" protocol="HTTP/1.1" scheme="http".../>

 

You don't seem to be providing much real information in any of your

posts.  At least tell us the exact Tomcat level and provide your actual

relevant config files.  (Your above sample, using <connector> rather

than <Connector>, is obviously not correct.)  In this instance, also

include the name and level of the browser you're using; there are known

issues in IE6 about mishandling redirects.  You might want to do a

packet capture so you can differentiate between what Tomcat's sending

and what the browser is deciding to interpret it as.

 

 - Chuck

 

 

THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY

MATERIAL and is thus for use only by the intended recipient. If you

received this in error, please contact the sender and delete the e-mail

and its attachments from all computers.

 

---------------------------------------------------------------------

To start a new topic, e-mail: users@tomcat.apache.org

To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org

For additional commands, e-mail: users-help@tomcat.apache.org

 


Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message