SSL-Zugang und Umlaute

tylerd — Tue, 27 Sep 2011 21:18:53 GMT

Hallo,seit etwa einer Woche nutze ich Alfresco 3.4d, wobei ich mich des Installers von der Alfresco-Website bedient habe, also mit mySQL und Tomcat 6.0.26.Ich habe es auch zwischenzeitlich geschafft, einen HTTPS-/SSL-Zugang einzurichten, nachdem ich neben der "Standardanleitung" eine weitere Zeile i

Re: SSL-Zugang und Umlaute

jpfi_4454 — Wed, 28 Sep 2011 05:54:25 GMT

Hi,
poste mal deine server.xml mit dem HTTPS-Connector. Das hört sich erstmal schwer nach fehlendem URIEncoding="UTF-8" in deinem HTTPS-Connector an.
VG, Jan

PS: Lösch bitte deinen Doppelpost

Re: SSL-Zugang und Umlaute

tylerd — Wed, 28 Sep 2011 11:50:14 GMT

Hallo Jan,

danke für die schnelle Antwort; ich wusste gar nicht, dass ich einen Post auch wieder löschen kann – erledigt!

URIencoding fehlt tatsächlich, das war aber so … Einfach wie bei HTTP Port 8080 übernehmen?

Gruß

TylerD

Hier noch meine Server.XML:

<?xml version='1.0' encoding='utf-8'?>
<!–
Licensed to the Apache Software Foundation (ASF) under one or more
contributor license agreements. See the NOTICE file distributed with
this work for additional information regarding copyright ownership.
The ASF licenses this file to You under the Apache License, Version 2.0
(the "License"); you may not use this file except in compliance with
the License. You may obtain a copy of the License at

      http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
–>
<!– Note: A "Server" is not itself a "Container", so you may not
     define subcomponents such as "Valves" at this level.
     Documentation at /docs/config/server.html
–>
<Server port="8005" shutdown="SHUTDOWN">

<!–APR library loader. Documentation at /docs/apr.html –>
<!–<Listener className="org.apache.catalina.core.AprLifecycleListener" SSLEngine="on" /> –>
<!–Initialize Jasper prior to webapps are loaded. Documentation at /docs/jasper-howto.html –>
<Listener className="org.apache.catalina.core.JasperListener" />
<!– Prevent memory leaks due to use of particular java/javax APIs–>
<Listener className="org.apache.catalina.core.JreMemoryLeakPreventionListener" />
<!– JMX Support for the Tomcat server. Documentation at /docs/non-existent.html –>
<Listener className="org.apache.catalina.mbeans.ServerLifecycleListener" />
<Listener className="org.apache.catalina.mbeans.GlobalResourcesLifecycleListener" />

<!– Global JNDI resources
       Documentation at /docs/jndi-resources-howto.html
–>
<GlobalNamingResources>
    <!– Editable user database that can also be used by
         UserDatabaseRealm to authenticate users
    –>
    <Resource name="UserDatabase" auth="Container"
              type="org.apache.catalina.UserDatabase"
              description="User database that can be updated and saved"
              factory="org.apache.catalina.users.MemoryUserDatabaseFactory"
              pathname="conf/tomcat-users.xml" />
</GlobalNamingResources>

<!– A "Service" is a collection of one or more "Connectors" that share
       a single "Container" Note: A "Service" is not itself a "Container",
       so you may not define subcomponents such as "Valves" at this level.
       Documentation at /docs/config/service.html
   –>
<Service name="Catalina">

    <!–The connectors can use a shared executor, you can define one or more named thread pools–>
    <!–
    <Executor name="tomcatThreadPool" namePrefix="catalina-exec-"
        maxThreads="150" minSpareThreads="4"/>
    –>


    <!– A "Connector" represents an endpoint by which requests are received
         and responses are returned. Documentation at :
         Java HTTP Connector: /docs/config/http.html (blocking & non-blocking)
         Java AJP Connector: /docs/config/ajp.html
         APR (HTTP/AJP) Connector: /docs/apr.html
         Define a non-SSL HTTP/1.1 Connector on port 8080
    –>
    <Connector port="8080" URIEncoding="UTF-8" protocol="HTTP/1.1"
               connectionTimeout="20000"
               redirectPort="8443" />
    <!– A "Connector" using the shared thread pool–>
    <!–
    <Connector executor="tomcatThreadPool"
               port="8080" protocol="HTTP/1.1"
               connectionTimeout="20000"
               redirectPort="8443" />
    –>
    <!– Define a SSL HTTP/1.1 Connector on port 8443
         This connector uses the JSSE configuration, when using APR, the
         connector should be using the OpenSSL style configuration
         described in the APR documentation –>

    <Connector port="8443" protocol="HTTP/1.1" SSLEnabled="true"
               maxThreads="150" scheme="https" secure="true"
               keystoreFile="D:/Alfresco/.keystore" keystorePass="Passwort"
               clientAuth="false" sslProtocol="TLS" />

    <!– Define an AJP 1.3 Connector on port 8009 –>
    <Connector port="8009" protocol="AJP/1.3" redirectPort="8443" />

    <!– An Engine represents the entry point (within Catalina) that processes
         every request. The Engine implementation for Tomcat stand alone
         analyzes the HTTP headers included with the request, and passes them
         on to the appropriate Host (virtual host).
         Documentation at /docs/config/engine.html –>

    <!– You should set jvmRoute to support load-balancing via AJP ie :
    <Engine name="Catalina" defaultHost="localhost" jvmRoute="jvm1">
    –>
    <Engine name="Catalina" defaultHost="localhost">

      <!–For clustering, please take a look at documentation at:
          /docs/cluster-howto.html (simple how to)
          /docs/config/cluster.html (reference documentation) –>
      <!–
      <Cluster className="org.apache.catalina.ha.tcp.SimpleTcpCluster"/>
      –>

      <!– The request dumper valve dumps useful debugging information about
           the request and response data received and sent by Tomcat.
           Documentation at: /docs/config/valve.html –>
      <!–
      <Valve className="org.apache.catalina.valves.RequestDumperValve"/>
      –>

      <!– This Realm uses the UserDatabase configured in the global JNDI
           resources under the key "UserDatabase". Any edits
           that are performed against this UserDatabase are immediately
           available for use by the Realm. –>
      <Realm className="org.apache.catalina.realm.UserDatabaseRealm"
             resourceName="UserDatabase"/>

      <!– Define the default virtual host
           Note: XML Schema validation will not work with Xerces 2.2.
       –>
      <Host name="localhost" appBase="webapps"
            unpackWARs="true" autoDeploy="true"
            xmlValidation="false" xmlNamespaceAware="false">

        <!– SingleSignOn valve, share authentication between web applications
             Documentation at: /docs/config/valve.html –>
        <!–
        <Valve className="org.apache.catalina.authenticator.SingleSignOn" />
        –>

        <!– Access log processes all example.
             Documentation at: /docs/config/valve.html –>
        <!–
        <Valve className="org.apache.catalina.valves.AccessLogValve" directory="logs"
               prefix="localhost_access_log." suffix=".txt" pattern="common" resolveHosts="false"/>
        –>

      </Host>
    </Engine>
</Service>
</Server>

Re: SSL-Zugang und Umlaute

tylerd — Wed, 28 Sep 2011 12:08:02 GMT

Hallo Jan,

update: Ich habe Deinen Vorschlag umgesetzt, den Dienst neu gestartet und … funktioniert auch mit Umlauten.

Vielen Dank

Gruß

TylerD

topic SSL-Zugang und Umlaute in Alfresco Archive

SSL-Zugang und Umlaute

Re: SSL-Zugang und Umlaute

Re: SSL-Zugang und Umlaute

Re: SSL-Zugang und Umlaute