Skip to main content
POST
History Forward

Overview

The /browser/sessions/{id}/forward endpoint moves the active tab one step forwards in its history stack, equivalent to clicking the browser’s forward button. The call blocks until the configured wait condition is met or the timeout elapses. When the browser’s back-forward cache is warm, this returns almost instantly. If there is no next history entry the endpoint returns 409 Conflict.

Path Parameters

string
required
Browser session ID (UUID). Create via POST /browser/sessions.

Body

All body fields are optional — the request body may be omitted entirely.
string
default:"load"
When to consider the navigation finished. One of load, domcontentloaded, networkidle.
integer
default:"30000"
Maximum time (ms) to wait for navigation. Range 0120000.

Example Request

Response

Success Response (200)

string
Effective URL of the active tab after moving forwards.
string
CDP target identifier of the tab the operation applied to.
Example Response:

Error Responses

Notes

  • Returns almost immediately when the browser’s back-forward cache (bfcache) is warm.
  • A 409 Conflict means there is nothing to go forward to — typically this happens after a fresh navigation, which wipes the forward stack.