headers can cause different reactions. a server may
serve a different version of a "page" depending on the
user-agent that requests it.
there can be a big difference between what you get with
httpjob and what you see in a browser. a browser is a
totally different animal. if you download a page with httpjob
and look at the text, you may see references to .css and
.js files. where are they? when a browser downloads the
same page, it automatically goes and downloads the
.css and .js files to complete the full page. httpjob does
not do this. you have to go back and download each of
those ancillary files by hand.
you stand a better chance of seeing what the browser
sees with webview and webviewextras. but even then,
there can be differences. you'd have to try. if you
study the page's source in chrome and see exactly how
it populates a given json object, you may well be able to
duplicate that behavior with webviewextras.