HTTP

Describe the bug
A clear and concise description of what the bug is.

To Reproduce
Steps to reproduce the behavior:

1. Go to realtime
2. Paste url wss://ris-live.ripe.net/v1/ws/?client=hoppscotch.io
3. Observe connect is disabled
4. Remove parameter, quickly undo it and click connect (also a bug)
5. Send { "type": "ris_subscribe" } to the remote server
6. Observe you receive

It would be a nice addition to integrate Minimal windows service stub in Caddy (built for Windows).

At the moment, it is necessary to use for example NSSM to install Caddy as a service on Windows.

See how it becomes much more natural to [install the service and remove it in the case of another project (Gitea) with the Windows tools](https:

When checking a request's remoteAddress, it's usually the address from which NIO received the request. While that's technically correct, Vapor servers are often hosted behind a reverse-proxy such as nginx. Therefore the original peer's address is often lost. To resolve this, it's not uncommon to set the original peer's address in a header such as X-Forwarded-For.

**Describe the solution you

Please reply the tasks you want to complete below, and I will assign them to you.
请在下方回复你要完成的任务，我会分配给你.

• #1981 @bingxindan
• #1967
• #1966 @Ccheers
• #1881 @pwli0755

If you're using proxies with requests-html and rendering JS sites is all good. Once you render a website pyppeteer don't know about this proxies and will expose your IP. This is an undesired behavior when scraping with proxies.

The idea is that whenever someone passes in proxies to the session object or any method call, make pyppeteer also use these proxies. #265

Is your feature request related to a problem?

While setting the target interface's ip should work in most cases, it's possible that multiple devices have the same ip.

Also i'm having trouble using a wireguard vpn when i set Table=off. Table=off disables setting up the routes for the vpn and it justs shows up as a regular device. The connection is fine as pycurl can access it when i set

This is a feature request, to display the valid SSL name (from the certificate) when starting up the server.

Steps to reproduce the issue, if applicable. Include the actual command and output and/or stack trace.

$ http-server -S

Starting up http-server, serving ./ through https
Available on:
  https://127.0.0.1:8080
  https://192.168.77.123:8080

**What did you exp

Context

This isn't really a feature request, as what I need is possible with nock as-is. But I spent several hours searching, reading old issues and searching through the source code to find the solution, so I thought this might help others.

I am testing code that accesses a service that sets the statusMessage of the response, as well as the statusCode. I am using nock to mock the server