On 21/03/2023 01:09, Ralph Grove wrote:
I'm having a problem installing a new SSL certificate on a GoDaddy-hosted
server running Tomcat. Any suggestions for resolving it would be appreciated.
I set up the server last year and installed the SSL certificate with no problem. This
year, after the
Hi there,
I am investigating an encoding problem in the compiler for tag files:
the following tag file (WEB-INF/tag/umlaut.tag):
<%@tag
trimDirectiveWhitespaces="true"
pageEncoding="UTF-8"
%>
<%= "ü does not work" %> // bytes c3 bc
(the file is in utf-8)
compiles into umlaut_tag.java in wh
> On Mar 21, 2023, at 4:25 AM, Mark Thomas wrote:
>
> On 21/03/2023 01:09, Ralph Grove wrote:
>> I'm having a problem installing a new SSL certificate on a GoDaddy-hosted
>> server running Tomcat. Any suggestions for resolving it would be appreciated.
>> I set up the server last year and insta
On 21/03/2023 09:17, Holger Klawitter wrote:
Hi there,
I am investigating an encoding problem in the compiler for tag files:
the following tag file (WEB-INF/tag/umlaut.tag):
<%@tag
trimDirectiveWhitespaces="true"
pageEncoding="UTF-8"
%>
<%= "ü does not work" %> // bytes c3 bc
(the file
Ralph,
On 3/21/23 06:38, Ralph Grove wrote:
> [snip]
>
Alias name: tomcat
Creation date: Mar 21, 2023
Entry type: trustedCertEntry
You created a keystore with no keys.
Where is the key you used to generate the CSR? That key needs to be in
your keystore under the alias 'tomcat' alongside t
Kevin,
On 3/20/23 20:12, Kevin Huntly wrote:
I actually fixed (well, figured out) the MySQL problem - it looks like it's
hard coded to a 2048b DH key, but I configured my servers for CIS level 2
which wants a minimum 3072. I can update the openssl config to utilize a
lower security level and it
"WTH" - holy heck! :D
Polymorphism, abstraction of interfaces .. standar OO, but definitely
not kids stuff to get everything to spec/standard (including the SQL
or proc invocations)!
:)
JDBC has been a very good interface despite/after O/R M challenges met.
Sysadmin is my second language to da
Follow-up to this thread:
I found the problem, which was my own mistake. I failed to enter the correct
domain name when creating the keystone. After going back through the entire
process again, with the correct domain name, the server is up and running
again. Thanks, nevertheless, for the help
