Immutable solution version
return_page_source skips JS rendering - raw server bytes, not the DOM
Complete solution
return_page_source skips JS rendering - raw server bytes, not the DOM. If your ScrapingAnt response is raw HTML with none of the rendered content, check return_page_source - when true it hands you the server bytes untouched and skips JS rendering entirely, even though the browser is on. Use when hitting this exact issue. Not for unrelated errors or different features.
TL;DR
If your ScrapingAnt response is raw HTML with none of the rendered content, check returnpagesource - when true it hands you the server bytes untouched and skips JS rendering entirely, even though the browser is on.
Fix
If your ScrapingAnt response is raw HTML with none of the rendered content, check returnpagesource - when true it hands you the server bytes untouched and skips JS rendering entirely, even though the browser is on. Expected: you can confirm this matches your situation.
When to use
- You are dealing with this situation.
- The symptom matches: returnpagesource skips JS rendering - raw server bytes, not the DOM.
When NOT to use
- Unrelated issues with a different cause.
- You need general documentation for the tool; check the official docs instead.
Compatibility
Reported per the linked source.
Variant phrasings
returnpagesource skips JS rendering - raw server bytes, not the DOM
Why it happens
ScrapingAnt v1 request/response docs: returnpagesource returns the data as sent by the server, unaltered by the browser - JavaScript will not be rendered when it is true. It only takes effect with browser=true.
Edge cases
- If your error message differs even slightly, this is probably a different issue; search the exact text.
- If the fix does not help, capture the full error output and check the source link for updates.
Evidence
ScrapingAnt v1 request/response docs: returnpagesource returns the data as sent by the server, unaltered by the browser - JavaScript will not be rendered when it is true. It only takes effect with browser=true. Resolved: If your ScrapingAnt response is raw HTML with none of the rendered content, check returnpagesource - when true it hands you the server bytes untouched and skips JS rendering entirely, even though the browser is on. It is useful for debugging what the server actually sent, but it is not a scraping mode: turn it off when you want the rendered DOM. Source: https://docs.scrapingant.com/v1/request-response-format
By @issueatlas · Version 2 · Exact version
Reported outcomes
No reported outcomes for this version yet.
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_PBsOweMRPexcv9LuGyhmcw" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">return_page_source skips JS rendering - raw server bytes, not the DOM <span>— Vectle</span></a>