## Summary

- **New Features**
- Introduced support for HTTP/2, enhancing web performance and reducing
latency.
- Added a new script for generating SSL certificates for local
development.
  
- **Bug Fixes**
- Updated response status checks to use integer values for better
accuracy in error handling.

- **Chores**
- Enhanced `.gitignore` to exclude self-signed certificates from version
control.
- Updated project dependencies to remove outdated libraries and include
HTTPX for improved performance.

- **Documentation**
- Revised `CHANGELOG.md` to reflect new features and deprecated
technologies.


## Expectation

When communicating between a Ruby server and a Node.js server via
HTTP/2, the speed difference compared to HTTP/1.1 largely depends on the
context and nature of the communication.

1. **On Localhost:**
- **Same Speed or Slightly Faster:** Since the servers are on the same
machine (localhost), there is minimal network latency. The overhead of
HTTP/2 multiplexing, header compression, and other optimizations might
not make a huge difference because the communication happens locally,
and the network itself isn't the bottleneck. However, HTTP/2 could be
slightly faster due to its ability to send multiple requests
concurrently over a single connection. But the difference will likely be
marginal.

2. **Between Different Servers (Over the Network):**
- **Likely Faster with HTTP/2:** When communicating with a different
server over a network (not localhost), HTTP/2's advantages become more
pronounced. These advantages include:
- **Multiplexing:** Multiple requests/responses can be in flight
simultaneously over the same TCP connection without head-of-line
blocking, which reduces latency, especially in high-latency networks.
- **Header Compression:** HTTP/2 compresses headers, reducing the size
of requests and responses, which can improve speed, especially when
there are many repetitive headers (e.g., cookies).
- **Reduced Connection Overhead:** Since HTTP/2 uses fewer connections
due to multiplexing, it reduces the overhead of setting up and tearing
down connections, which can lead to faster communication, especially in
environments with higher latency.

### Summary:
- **On localhost:** The difference in speed between HTTP/2 and HTTP/1.1
will likely be negligible, though HTTP/2 might be marginally faster due
to multiplexing.
- **Over the network:** HTTP/2 will generally be faster due to
multiplexing, header compression, and reduced connection overhead,
especially in scenarios with higher latency or when multiple requests
are being made concurrently.

Closes #379.



<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit

## Release Notes

- **New Features**
- Introduced streaming server rendering support for improved performance
and progressive page loading.
- Added replay functionality for console logs during server rendering to
aid debugging.
- Enhanced error handling during server rendering with new configuration
options.
- Integrated support for HTTP/2 in the node-renderer for better
performance.

- **Bug Fixes**
	- Improved error reporting and handling for HTTP requests.
	- Updated multiple JavaScript dependencies for better stability.

- **Documentation**
	- Updated `CHANGELOG.md` to reflect new features and changes.

- **Tests**
- Modified tests to accommodate new HTTP/2 request handling and improved
error management.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->

---------

Co-authored-by: Alexey Romanov <[email protected]>

## Summary

- **New Features**
- Introduced support for HTTP/2, enhancing web performance and reducing
latency.
- Added a new script for generating SSL certificates for local
development.
  
- **Bug Fixes**
- Updated response status checks to use integer values for better
accuracy in error handling.

- **Chores**
- Enhanced `.gitignore` to exclude self-signed certificates from version
control.
- Updated project dependencies to remove outdated libraries and include
HTTPX for improved performance.

- **Documentation**
- Revised `CHANGELOG.md` to reflect new features and deprecated
technologies.


## Expectation

When communicating between a Ruby server and a Node.js server via
HTTP/2, the speed difference compared to HTTP/1.1 largely depends on the
context and nature of the communication.

1. **On Localhost:**
- **Same Speed or Slightly Faster:** Since the servers are on the same
machine (localhost), there is minimal network latency. The overhead of
HTTP/2 multiplexing, header compression, and other optimizations might
not make a huge difference because the communication happens locally,
and the network itself isn't the bottleneck. However, HTTP/2 could be
slightly faster due to its ability to send multiple requests
concurrently over a single connection. But the difference will likely be
marginal.

2. **Between Different Servers (Over the Network):**
- **Likely Faster with HTTP/2:** When communicating with a different
server over a network (not localhost), HTTP/2's advantages become more
pronounced. These advantages include:
- **Multiplexing:** Multiple requests/responses can be in flight
simultaneously over the same TCP connection without head-of-line
blocking, which reduces latency, especially in high-latency networks.
- **Header Compression:** HTTP/2 compresses headers, reducing the size
of requests and responses, which can improve speed, especially when
there are many repetitive headers (e.g., cookies).
- **Reduced Connection Overhead:** Since HTTP/2 uses fewer connections
due to multiplexing, it reduces the overhead of setting up and tearing
down connections, which can lead to faster communication, especially in
environments with higher latency.

### Summary:
- **On localhost:** The difference in speed between HTTP/2 and HTTP/1.1
will likely be negligible, though HTTP/2 might be marginally faster due
to multiplexing.
- **Over the network:** HTTP/2 will generally be faster due to
multiplexing, header compression, and reduced connection overhead,
especially in scenarios with higher latency or when multiple requests
are being made concurrently.

Closes #379.



<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit

## Release Notes

- **New Features**
- Introduced streaming server rendering support for improved performance
and progressive page loading.
- Added replay functionality for console logs during server rendering to
aid debugging.
- Enhanced error handling during server rendering with new configuration
options.
- Integrated support for HTTP/2 in the node-renderer for better
performance.

- **Bug Fixes**
	- Improved error reporting and handling for HTTP requests.
	- Updated multiple JavaScript dependencies for better stability.

- **Documentation**
	- Updated `CHANGELOG.md` to reflect new features and changes.

- **Tests**
- Modified tests to accommodate new HTTP/2 request handling and improved
error management.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->

---------

Co-authored-by: Alexey Romanov <[email protected]>