Page context, proxy simplicity

Send requests through pages

Use HttpProxyAgent to route existing Axios requests through a real browser page, keeping session context without CDP automation.

View example How it works

0 Total requests

0 Total sites

0 Online clients

Use it like a proxy

Axios through PageProxy

pageproxy-demo.js

Minimal client changes

The caller still sends an ordinary HTTP request. PageProxy handles the browser-side fetch, optional header enrichment, and streaming response path.

HTTP proxy entry on port 80
WebSocket extension connection on 443
Shared client pool with passwd protected
Optional page-context header hook

Browser pool

Your page anywhere

Point Axios at PP, choose a target page host, and let the browser that already has the session send the request.

Axios HttpProxyAgent

PageProxy

Work page session ready

Personal page cookies intact

Shared pool passwd protected

FAQ

Before you proxy

How is this different from CDP automation?

PageProxy is not a browser control framework. It is a proxy path that uses a page as the request executor, so existing HTTP clients can keep their normal request shape.

Why use page context?

Some APIs depend on session, storage, cookies, or page-side state. PP lets the proxy request run where that state already exists.

Can it add authorization headers?

Yes. The optional x-proxy-client-script header can run a small header hook before fetch and merge the returned headers into the proxied request.

Does shared mode need protection?

Yes. Direct clients use UUID usernames with empty passwords. Shared mode uses the wildcard username with a fixed Basic Auth password.

Is PageProxy free?

Yes. You can use PageProxy for free with a limit of 10 requests every 5 seconds.