These are referenced at the end of httpd.conf (this line shoould already be there. if not simply add it)
# WebObjects 5.4: Enable the WebObjects module.
#LoadModule WebObjects_module /Library/WebObjects/Adaptors/mod_WebObjects.so
LoadModule WebObjects_module /Users/Shared/Developer/Libraries/Wonder/woadaptor_pr992_fixed/Apache2.4/macOS_Intel/mod_WebObjects.so
# You can change the 'cgi-bin' part of WebObjectsAlias to whatever you
# prefer (such as Apps), but the 'WebObjects' part is required.
WebObjectsAlias /apps/WebObjects
<Location /apps/WebObjects/>
<Limit GET POST OPTIONS >
Require all granted
</Limit>
Require all denied
</Location>
# Here are the 3 possible configuration modes.
# The apache module uses one of them to get information
# about your deployed applications.
# 1085 is the reserved port on which wotaskd processes listen to by default.
# Host List Configuration
# wotaskd is started automatically on supported platforms,
# so this is the default mode.
# The apache module gets its configuration from the wotaskds
# listed on the configuration line
# For multiple hosts:
# WebObjectsConfig http://<name-of-a-host>:<port-on-a-host>,http://<name-of-another-host>:<port-on-a-host> <interval>
# For localhost:
WebObjectsConfig http://woapps:1085 10
# Multicast Configuration
# The apache module gets its configuration from all wotaskds
# that respond to the multicast call on the subnet
# WebObjectsConfig webobjects://239.128.14.2:1085 10
# File Configuration
# The apache module gets its configuration from one file
# WebObjectsConfig file://<path-to-a-xml-config-file> 10
# To enable public access to the WOAdaptorInfo page, uncomment the following line
# WebObjectsAdminUsername public
# To enable the WOAdaptorInfo page with restricted access,
# uncomment the next two lines and set the user and password
# To access the WOAdaptorInfo page with restricted access,
# use a URL like: http://webserver/cgi-bin/WebObjects/WOAdaptorInfo?user+password.
# WebObjectsAdminUsername user
# WebObjectsAdminPassword password
# To change the logging options, read the following comments:
# The option name is "WebObjectsLog" and the first value indicates the path of the log file.
# The second value indicates the log level. There are five, in decreasing informational order:
# "Debug", "Info", "Warn", "Error", "User"
#
# Note: To enable logging, touch '/tmp/logWebObjects' as the administrator user (usually root).
#
# The following line is the default:
# WebObjectsLog /Library/WebObjects/Logs/WebObjects.log Debug
$ cat /usr/local/etc/httpd/other/wo_expires.conf
## File for Expires
<IfModule mod_expires.c>
ExpiresActive On
ExpiresDefault A60
ExpiresByType image/x-icon A3600
ExpiresByType application/x-javascript A3600
ExpiresByType text/css A3600
ExpiresByType image/gif A3600
ExpiresByType image/png A3600
ExpiresByType image/jpeg A3600
ExpiresByType application/x-shockwave-flash A3600
ExpiresByType video/x-flv A3600
ExpiresByType application/pdf A3600
</IfModule>
$ cat less /usr/local/etc/httpd/other/wo_rewrite.conf
## File for Rewrite
<IfModule mod_rewrite.c>
## RewriteEngine On
## RewriteRule ^/$ /page/HomePage [R]
## RewriteCond %{QUERY_STRING} ^appNum=([-0-9]+)(.*)$
## RewriteRule ^/page/(.*)$ /cgi-bin/WebObjects/AppName.woa/%1/wa/viewPage?pageName=$1%2 [L,PT]
## RewriteRule ^/page/(.*)$ /cgi-bin/WebObjects/AppName.woa/wa/viewPage?pageName=$1 [L,PT,QSA]
</IfModule>
You cannot run https with a letsencrypt certificate because your sites are not publicly reachable. You can however create your own CA and cert if you really want to be that fancy (use KeychainAccess.app on the Mac). I never bothered though.
Be careful when you try to connect with your web browser. Browsers usually play tricks with the URL and add https and www and other niceties and that will fail to open your single name domain. You must specify the whole URL so that the browser does not have to second guess and break the final address.
HAVE FUN, there is a whole weekend coming up.......