You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The discussion revolves around configuring BunHttpServer for HTTPS. It is indeed possible to configure BunHttpServer to use HTTPS by passing tls options to the layer constructor. However, there's a noted issue with the type definitions where ServeOptions are mistakenly used instead of Serve<WebSocketDataType>. The corrected type, as provided, includes various options for serving over TLS, including TLSServeOptions and TLSWebSocketServeOptions, among others, to accommodate different configurations such as Unix sockets and WebSocket data types.
Key takeaways include:
BunHttpServer supports HTTPS configuration through tls options.
There's a type definition issue in the library that may affect implementation.
The corrected type definition expands the options to include TLS and WebSocket configurations, providing a comprehensive approach for HTTPS setup.
Summary
The discussion revolves around configuring BunHttpServer for HTTPS. It is indeed possible to configure BunHttpServer to use HTTPS by passing
tls
options to thelayer
constructor. However, there's a noted issue with the type definitions whereServeOptions
are mistakenly used instead ofServe<WebSocketDataType>
. The corrected type, as provided, includes various options for serving over TLS, includingTLSServeOptions
andTLSWebSocketServeOptions
, among others, to accommodate different configurations such as Unix sockets and WebSocket data types.Key takeaways include:
tls
options.Discord thread
https://discord.com/channels/795981131316985866/1238180224529731654
The text was updated successfully, but these errors were encountered: