How to Make CasperJS Follow Links on ASP.NET Sites

If a link on an ASP.NET Web Forms page points to a normal URL, use CasperJS’s thenClick() or click() to activate it. If the rendered link calls __doPostBack(...), it is a form action rather than an ordinary destination: click the actual control, preserve the page’s form state, and verify that the results changed instead of relying on the URL alone.

CasperJS is legacy software: its project says it is no longer actively maintained. The guidance below is for understanding and maintaining existing CasperJS automation, not a comparison of current browser-automation frameworks.

#	Preview	Product	Price
1		Instant Testing with CasperJS	$10.69	Buy on Amazon

First identify what the link actually does

A visible “Next” link can represent different browser behavior. Inspect the rendered element in the page, not just its label or the source template. The distinction determines whether CasperJS should navigate to a URL or trigger an ASP.NET event.

Microsoft’s ASP.NET 2.0 Page Model documentation explains: “Remember that __doPostBack programmatically submits the form on the page.” A Web Forms control may therefore look like a hyperlink without having a standalone next-page URL. Whether it submits the full form, uses a callback, changes the URL, or depends on particular hidden fields varies by page implementation. Microsoft’s page-model documentation describes the mechanism.

#1 Best Overall

Sale

Instant Testing with CasperJS

$10.69

Buy on Amazon

Use CasperJS’s built-in click for the rendered control

For a conventional link or a Web Forms control that is present and clickable in the page, start with CasperJS’s selector-based click action. Its API describes thenClick(selector[, callback]) as a navigation step that clicks the matching element. Use a selector that identifies the specific pager control rather than a broad selector that might match several links.

var casper = require('casper').create();

casper.start('https://example.com/results', function () {
    this.thenClick('a.next-page', function () {
        this.echo('After click: ' + this.getCurrentUrl());
    });
});

casper.run();

Replace the example URL and selector with the target site’s address and rendered control. A selector can be based on a stable ID, class, or other attribute from the live markup. For a real-URL anchor, a changed URL is a useful check. For a postback control, the URL may stay the same even when the server processes the requested page change.

CasperJS also offers click() for a matching DOM element. Use it when that action fits the sequence in your existing script; use thenClick() when you want the click represented as a step in the CasperJS navigation flow. Both approaches target the rendered control, allowing the page’s own event handling to run.

Inspect the ASP.NET markup and form state

Before trying to construct a request yourself, inspect the live element and the form it belongs to. In particular, note its href, any onclick handler, the containing form, and relevant hidden inputs. A Web Forms postback can depend on generated event data and hidden form state; sending only a displayed control ID or guessing a postback target can omit information the page needs.

this.echo(this.evaluate(function () {
    var link = document.querySelector('a.next-page');
    if (!link) {
        return 'Next link not found';
    }

    var form = link.form || link.closest('form');
    return JSON.stringify({
        href: link.getAttribute('href'),
        onclick: link.getAttribute('onclick'),
        formId: form ? form.id : null,
        hiddenFields: form ? Array.prototype.map.call(
            form.querySelectorAll('input[type="hidden"]'),
            function (input) {
                return { name: input.name, value: input.value };
            }
        ) : []
    });
}));

evaluate() executes its function in the current page’s DOM context, so the code inside it can read browser-side elements and attributes. It is not the same context as the surrounding CasperJS script. Use it to inspect or, if necessary, activate the actual rendered element; do not treat it as permission to discard the site’s form state. CasperJS’s API also recommends fill() for filling and submitting forms when a form workflow is required. See the CasperJS API documentation.

Wait for the result, then prove it changed

A click event completing does not establish that the server returned the intended results. Choose a result-specific condition: for example, a new page indicator, a changed result row, or text that appears only on the requested page. Prefer a condition tied to the desired state over a fixed delay. CasperJS documentation notes that timing failures can happen when a resource or element is not yet available and describes waiting for nodes, text, or resources before continuing.

casper.start('https://example.com/results', function () {
    this.thenClick('a.next-page');

    this.waitFor(function () {
        return this.exists('.results-page[data-page="2"]');
    }, function () {
        this.echo('Page 2 results appeared');
    }, function () {
        this.echo('Timed out waiting for page 2 results');
    }, 10000);
});

casper.run();

The selector in this example is illustrative; use an indicator the actual page exposes and that changes when the requested results arrive. A URL assertion can complement the check for a normal navigation link, but it is not enough for every Web Forms pager.

When the result does not appear, compare multiple signals instead of trusting one. A selected pager label could change while the data remains unchanged. Check the result rows or text, relevant hidden values, and request or response activity where available. A historical 2015 Stack Overflow report describes a site-specific case where a page indicator appeared to change after a jQuery click while screenshot results looked unchanged. It illustrates why verification matters, not a universal CasperJS defect or a guaranteed fix. Read the reported example.

Use page-context evaluation only when a normal click is insufficient

If CasperJS cannot activate the element as expected, inspect the page’s handlers and rendered markup first. A page-context DOM click can be a diagnostic or fallback, but it does not fix missing server state, validation failures, authentication problems, or script errors.

this.evaluate(function () {
    var link = document.querySelector('a.next-page');
    if (link) {
        link.click();
    }
});

Run this from a CasperJS step after the page and element are available. Then wait for a meaningful result condition as described above. Do not fabricate a bare request from a guessed __doPostBack target: the generated event arguments and current form fields can be essential to the server-side action.

Troubleshoot unchanged or missing results

• The selector finds no element: inspect the rendered HTML after the page has loaded. The selector may not match the live pager, or the control may not yet exist. Wait for the element before clicking.
• The href is a real URL but the script stays put: check that the selector matches the intended anchor and that the click step ran. Wait for the destination content or navigation rather than assuming an immediate URL read is conclusive.
• The href contains javascript:__doPostBack(...): treat the control as a Web Forms form event. Click the rendered control first; inspect its form and hidden fields rather than substituting a guessed URL.
• The URL stays the same: this can be normal for a postback or callback. Verify result rows, page selection, changed state, or request/response data.
• The page label changes but results do not: a label alone does not prove that the requested data loaded. Compare the data itself and inspect server response and network activity.
• The click works intermittently: wait for the relevant element, text, or result condition. A longer arbitrary delay may hide a race without ensuring the desired state.
• Nothing changes after the click: capture rendered HTML and logs, check page errors and network activity, and compare the expected postback parameters and form fields with what the browser submits. Investigate site-specific validation, authentication, and script errors before increasing waits.

CasperJS’s waiting guidance is in its API documentation. The correct result condition and the form data required by a particular ASP.NET site are site-specific.

Or skip the browser setup

If you only need a screenshot of the results page—not to automate its pager or inspect its underlying data—you can request a capture from ScreenshotNeo, a website screenshot API and MCP server for developers. Its capture options include clicking an element before capture and waiting for a selector, delay, or network idle; that is a screenshot workflow, not a replacement for testing a Web Forms postback.

curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://example.com/results -o shot.webp

See the ScreenshotNeo API documentation for request options. Cookie banners, newsletter popups, and chat widgets are removed before capture; bot checks, blank pages, and failed loads are never billed. Its MCP server lets AI agents take screenshots. The free plan includes 1,000 screenshots a month with no card, and paid plans start at $5 for 3,000. Sign up for ScreenshotNeo’s free plan.

Know the limits of this legacy workflow

The CasperJS API guidance referenced here is from its legacy documentation, and the project repository states that “CasperJS is no longer actively maintained.” Existing teams can use these techniques to diagnose old suites, but the documentation does not establish which current alternative is best or provide a migration recommendation. See the CasperJS project repository.

Frequently Asked Questions

Does an ASP.NET Web Forms pager always change the URL?

No. A postback or callback can update page state or content without changing the URL; confirm the results with a page-specific signal.

Should I call `__doPostBack` directly from CasperJS?

Usually start by clicking the rendered control. Directly recreating a postback can omit generated event data or hidden form state.

Quick Recap

SaleBestseller No. 1

Instant Testing with CasperJS

$10.69

Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.