Active Oldest Votes. Improve this answer. Jonas Felber Jonas Felber 2 2 silver badges 13 13 bronze badges. Vtin Vtin 61 1 1 silver badge 8 8 bronze badges. Sign up or log in Sign up using Google. Sign up using Facebook. Sign up using Email and Password. Post as a guest Name. Email Required, but never shown. The Overflow Blog. Thank you. Usage of cookies: In order to optimize the website and for continuous improvement vcloud-lab. You agree to the usage of cookies when you continue using this site.
Virtual Geek Tales from real IT system administrators world and non-production environment. Posted in Powershell.
Tags powershell ssl https certificate winrm wsman. Enter text only if you are not human:. Blog Search. Comments Johan. December 17, AM. I think Rudy would appreciate it too. I registered a Letsencrypt Certificate. Content: Wordpress CMS. The Website worked well. Last week I switched to a new "Server": Windows Instead of using IIS I decided to use apache.
I did a completely new registration of the Letsencrypt certificate. In other words: I did'nt care for the certificated on the "old" server. The website up to now is magicmamaweb. Until last week there was a permanent redirection from magicmama. I'm not sure when I registered the certificate for magicmama. The redirection from magicmama. Last week I changed the pointer of magicmama. Since then I have these problems. The same index. If I don't use a proxy then my router doesn't route correct.
Thanks for that info. You confirm you are seeing what I described in post 5. The problem is not related to your certs. It is a problem with Apache choosing the wrong VirtualHost to process an incoming request.
Only after Apache chooses the VHost does it look at the certs. That is how it should work and SNI has been around a long time so usually does work. But, oddly, your Apache behaves as if it is not working right. There are other Apache sources of documentation for this too.
I am not certain it is related to a broken SNI but if not that then something else related to Apache's virtual host selection process. You could prove to yourself that this is not related to the certs by placing the VirtualHost for magicmama before the other one.
I described this in post 5. That would make magicmama the default server for port requests. You should also review your Apache error logs. That should show some info about what is happening. This is described in the wiki I link to above. I do not know Windows and Apache well enough to assist further.
The priority of the acceptor threads. The threads used to accept new connections. The default value is 5 the value of the java. See the JavaDoc for the java. Thread class for more details on what this priority means. For servers with more than one IP address, this attribute specifies which address will be used for listening on the specified port. By default, the connector will listen all local addresses.
By default Tomcat will allow requests that specify a host in the request line but specify a different host in the host header.
This check can be enabled by setting this attribute to false. If not specified, the default is true. By default Tomcat will ignore all trailer headers when processing chunked input. For a header to be processed, it must be added to this comma-separated list of header names. Controls when the socket used by the connector is bound.
By default it is bound when the connector is initiated and unbound when the connector is destroyed. If set to false, the socket will be bound when the connector is started and unbound when it is stopped. When client certificate information is presented in a form other than instances of java. XCertificate it needs to be converted before it can be used and this property controls which JSSE provider is used to perform the conversion.
If not specified, the default provider will be used. If you specify a type explicitly, the default is over-ridden. The acceptable values for the parameter is "off" disable compression , "on" allow compression, which causes text data to be compressed , "force" forces compression in all cases , or a numerical integer value which is equivalent to "on", but specifies the minimum amount of data before the output is compressed.
If the content-length is not known and compression is set to "on" or more aggressive, the output will also be compressed. If not specified, this attribute is set to "off".
Note: There is a tradeoff between using compression saving your bandwidth and using the sendfile feature saving your CPU cycles. If the connector supports the sendfile feature, e.
The symptoms will be that static files greater that 48 Kb will be sent uncompressed. If compression is set to "on" then this attribute may be used to specify the minimum amount of data before the output is compressed.
If not specified, this attribute is defaults to "". Units are in bytes. The number of seconds during which the sockets used by this Connector will linger when they are closed. The default value is -1 which disables socket linger. The number of milliseconds this Connector will wait, after accepting a connection, for the request URI line to be presented. Use a value of -1 to indicate no i. The default value is i. Unless disableUploadTimeout is set to false, this timeout will also be used when reading the request body if any.
Specifies the timeout, in milliseconds, to use while a data upload is in progress. This only takes effect if disableUploadTimeout is set to false.
This flag allows the servlet container to use a different, usually longer connection timeout during data upload. If not specified, this attribute is set to true which disables this longer timeout.
A reference to the name in an Executor element. If this attribute is set, and the named executor exists, the connector will use the executor, and all the other thread attributes will be ignored. Note that if a shared executor is not specified for a connector then the connector will use a private, internal executor to provide the thread pool. The time that the private internal executor will wait for request processing threads to terminate before continuing with the process of stopping the connector.
If not set, the default is 5 seconds. The number of milliseconds this Connector will wait for another HTTP request before closing the connection. The default value is to use the value that has been set for the connectionTimeout attribute. The maximum number of connections that the server will accept and process at any given time. When this number has been reached, the server will accept, but not process, one further connection. This additional connection be blocked until the number of connections being processed falls below maxConnections at which point the server will start accepting and processing new connections again.
Note that once the limit has been reached, the operating system may still accept connections based on the acceptCount setting. The default value varies by connector type. The maximum number of cookies that are permitted for a request.
A value of less than zero means no limit. If not specified, a default value of will be used. Limits the total length of chunk extensions in chunked HTTP requests.
If the value is -1, no limit will be imposed. If not specified, the default value of will be used. The maximum size of the request and response HTTP header, specified in bytes. If not specified, this attribute is set to 8 KB.
The maximum number of HTTP requests which can be pipelined until the connection is closed by the server. Setting this to -1 will allow an unlimited amount of pipelined or keep-alive HTTP requests.
If not specified, this attribute is set to The maximum number of request body bytes excluding transfer encoding overhead that will be swallowed by Tomcat for an aborted upload. An aborted upload is when Tomcat knows that the request body is going to be ignored but the client still sends it.
If Tomcat does not swallow the body the client is unlikely to see the response. If not specified the default of 2 megabytes will be used. A value of less than zero indicates that no limit should be enforced. The maximum number of request processing threads to be created by this Connector, which therefore determines the maximum number of simultaneous requests that can be handled.
If an executor is associated with this connector, this attribute is ignored as the connector will execute tasks using the executor rather than an internal thread pool. Note that if an executor is configured any value set for this attribute will be recorded correctly but it will be reported e. Limits the total length of trailing headers in the last chunk of a chunked HTTP request.
The minimum number of threads always kept running. This includes both active and idle threads. If not specified, the default of 10 is used. This flag configures whether resources with a strong ETag will be considered for compression. If true, resources with a strong ETag will not be compressed.
0コメント