Marcel Waldvogel

993 should **not** support `STARTTLS`. Instead, it is "Implicit TLS". Implicit TLS is what HTTPS does: Directly start the TLS handshake, and only after this is successful, send any date...

If a context menu might not be the best choice, how about having a place to add local words to a whitelist?

Yes, removing those many long stack traces from the terminal output would definitely help keeping track of the actual problem. So then the reason it won't build is probably further...

Commented out the `@Test` in front of `should_convert_large_diagram()` and `should_return_an_unicode_text_diagram()` as a temporary workaround. Now the jars lie in `server/target`, so I can continue building.

Indeed, compiling on 20.04 (with OpenJDK, `apt install maven openjdk-11-jdk-headless`) works like a charm. ```shell $ cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=21.10 DISTRIB_CODENAME=impish DISTRIB_DESCRIPTION="Ubuntu 21.10" ``` ```sh $ mvn --version Apache Maven...

So, `Last-Modified` would just be the current date? (I think dropping it would not be helpful/necessary) I see no `ETag` handling in the code, just `ETag` creation. So, the caching...

I'm in favor of outsourcing complexity to someone who already has implemented it instead of implementing it on my own. So, unless this is a real issue (I do not...

It seems that the design for `Last-Modified` is clear, i.e., that it should be the time at which the code was built, as the result will only depend on the...

Build time as `Last-Modified` is now included in #1065, together with tests.

Agreeing with @tribela : Could you please change `unsafe-eval` to `wasm-unsafe-eval`? It is supported by all current platforms and avoids `eval` loopholes. https://caniuse.com/?search=wasm-unsafe-eval