feat: Add content to the Jakarta Servlet Spec page

[ZacharySabourin]

Resolves https://github.com/jakartaee/jakarta.ee/issues/1751

[netlify[bot]]

✅ Deploy Preview for jakartaee-specifications ready!

Name	Link
🔨 Latest commit	44effcf991c9b43ebe86e46f1f6b76141c59bbbe
🔍 Latest deploy log	https://app.netlify.com/sites/jakartaee-specifications/deploys/657ca66a76124d000832ff55
😎 Deploy Preview	https://deploy-preview-684--jakartaee-specifications.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[ZacharySabourin]

@chrisguindon

[ZacharySabourin]

@ivargrimstad Preview page: https://deploy-preview-684--jakartaee-specifications.netlify.app/specifications/servlet/

[ivargrimstad]

Request for project team to review: https://www.eclipse.org/lists/servlet-dev/msg00627.html

[pmd1nh]

https://deploy-preview-684--jakartaee-specifications.netlify.app/specifications/servlet/6.1/

Minimum Java SE Version

Java SE 11 or higher

Should it be Java 17 or higher?

[markt-asf]

Nope. At this point Servlet requires Java 11 minimum.

[joakime]

Nope. At this point Servlet requires Java 11 minimum.

Servlet 6.1 is for EE11, which is minimum JDK 17. Specs are free to compile for a lower JDK. BUT! Implementations must pass TCK on JDK 17 and JDK 21.

Jetty has been on JDK 17 and JDK 21 for a while now, and JDK 17 behaves differently to JDK 11 in some key areas that can impact Servlet TCK. One interesting behavior change is with how the JDK provided Writer implementations now flush in close on JDK 17+ but not on JDK 11. This has caused "interesting" behaviors with regards to Content-Length vs Transfer-Encoding chunked on responses.

• The bug that caused this Writer behavior change - https://bugs.openjdk.org/browse/JDK-8220477
• The change - https://hg.openjdk.org/jdk/jdk/rev/7689e1cc56fe