inspector: fix absolute URLs in network http

[GrinZero]

Summary

This PR fixes incorrect URL reporting in the HTTP network inspector when a client passes an absolute URL as options.path.

Before this change, the inspector always constructed the request URL as:

request.protocol + '//' + host + request.path

That works for normal relative paths such as /hello-world, but it breaks when request.path already contains a full URL, producing values like:

http://127.0.0.1:3000http://127.0.0.1:3000/hello-world

As a result, DevTools shows an incorrect Request URL in Network.requestWillBeSent and Network.responseReceived.

Problem

Observed behavior:

request.path shape	Previous inspector URL	Expected URL
/hello-world	http://127.0.0.1:3000/hello-world	http://127.0.0.1:3000/hello-world
http://127.0.0.1:3000/hello-world	http://127.0.0.1:3000http://127.0.0.1:3000/hello-world	http://127.0.0.1:3000/hello-world

This was reproducible with HTTP clients that forward an absolute URL through the path field.

Solution

The fix keeps the existing behavior for relative paths and adds a guard for absolute URL paths.

Behavior after this change:

• If request.path starts with http:// or https://, use it directly.
• Otherwise, keep constructing the URL from protocol, host, and path.

This keeps the patch small and isolates it from the compressed-response work, which will be handled separately.

Tests

The existing HTTP inspector test was extended to cover:

• relative-path GET
• absolute-URL-path GET
• absolute-URL-path POST

The POST case also verifies that Network.getResponseBody() still returns the expected payload.

[nodejs-github-bot]

Review requested:

• @nodejs/inspector

[GrinZero]

E2E:

const axios = require('axios')
const Koa = require('koa')
const Router = require('koa-router')

const app = new Koa()
const router = new Router()

router.get('/', async (ctx) => {
  const res = await axios.get('https://jsonplaceholder.typicode.com/posts')
  ctx.body = res.data
})

app.use(router.routes())
app.listen(3000)

• before:

• after: