<!DOCTYPE html>
<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body>
<p><font face="monospace">Hi all,</font></p>
<p><font face="monospace">Quick status update on the IMS work:
today we merged the new "http2d" module on master branch,
providing HTTP/2 server-side support in OpenSIPS. Here are some
resources around it:<br>
</font></p>
<p><font face="monospace"><span
class="selectable-text copyable-text">Docs: <a
href="https://opensips.org/docs/modules/3.5.x/http2d.html#overview"
class="moz-txt-link-freetext">https://opensips.org/docs/modules/3.5.x/http2d.html#overview</a><br>
Blog: <a
href="https://blog.opensips.org/2024/03/27/http-2-server-support-for-next-generation-services-in-opensips-3-5/"
class="moz-txt-link-freetext">https://blog.opensips.org/2024/03/27/http-2-server-support-for-next-generation-services-in-opensips-3-5/</a></span></font></p>
<p><font face="monospace"><span
class="selectable-text copyable-text">Any feedback is
appreciated. From our side, the only question for now is
related to "h2c" (HTTP/2 cleartext) support -- whether we
should consider adding it or not. Because while it may seem
useful, major browser vendors did not reach the same
conclusion some years ago, as Google and Firefox will still
not connect via HTTP/2 "h2c" cleartext to an HTTP/2 server
with no TLS support. Is it the same case for the 5GC? Any
relevant 3GPP doc hints around HTTP/2 usage would be very
helpful here.</span></font></p>
<font face="monospace">Best regards,</font><br>
<p></p>
<pre class="moz-signature" cols="72">--
Liviu Chircu</pre>
</body>
</html>