Re: [jetty-users] Easiest jetty replacement?

[Bill Ross <bross_phobrain@xxxxxxxxx>]

> What problems are you having specifically with https?

I tried to get it working two times at least a year apart with certificates (2nd time with the free, self-renewing one), and gave up each time. 

Maybe the third time will be the charm.

> admittedly we terminate TLS with our host's appliance

https://en.wikipedia.org/wiki/The_Gods_Must_Be_Crazy

I was tempted to port/rewrite to a js or python server for even more of that codebase purification. :-)

The main use is on a local machine, so normal users shouldn't need certificates.

Latest thought is make it a back-end java server, so the web server would be a minimal layer using my API.

It would be a return to the hand-rolled distributed computing/roboting that I was doing in the 80's in C:

http://phobrain.com/pr/home/nastore/index.html

The man pages are on an offline drive somewhere, but their names alone could give an idea of the concept:

 

http://phobrain.com/pr/home/nastore/doc/manpages.html

 

Bill

 

--

 

https://github.com/phobrain/Phobrain/tree/main

Phobrain.com

---

 

On 2026-03-06 18:16, Steven Schlansker wrote:

On Mar 6, 2026, at 4:20 PM, Bill Ross via jetty-users <jetty-users@xxxxxxxxxxx> wrote:

I'm looking to change from Jetty, now that I have to pay for upgrades to 10.x for my hobby site.
12.x is problematic for me since I haven't been able to get https working.
I've got 41K of Servlet code.
Ideas?

Probably the easiest upgrade path is to Jetty 12.x.
I agree, who would pay to run outdated versions, what nonsense! :P
(What other response do you expect, asking the Jetty community?)

You didn't include any real details about your problem. But (total stab in the dark) if you're mostly concerned about
the change from 'javax' to 'jakarta', I think unfortunately you'll find that the lawyers won, the community is moving on,
and you will have to bite the bullet sooner or later. Unfortunate that technical pain follows from legal politics
but such is life sometimes. For the most part global find and replace does at least some of the work, you'll fix a
metric ton of problems along the way, and emerge with a much better codebase overall.

What problems are you having specifically with https? We upgraded to Jetty 12.1 and are happier than ever with Jetty,
although admittedly we terminate TLS with our host's appliance and not Jetty itself.