{"id":136,"date":"2011-07-01T14:17:28","date_gmt":"2011-07-01T14:17:28","guid":{"rendered":"http:\/\/thewiredguy.com\/wordpress\/?p=136"},"modified":"2011-07-01T14:17:28","modified_gmt":"2011-07-01T14:17:28","slug":"dont-have-an-apirip-dat-off-the-page","status":"publish","type":"post","link":"https:\/\/inullable.in\/blog\/?p=136","title":{"rendered":"Stuck! No API, rip data off the page"},"content":{"rendered":"

You want to use some data that is provided by some site, but they doesn\u2019t expose any API to get that data. Well, a possible (and a very dirty) trick is to get the page HTML and rip data off it for our use.<\/p>\n

Not so easy dude… there are many hurdles:<\/p>\n

  • First one is the \u201cSame origin policy<\/a>\u201d security restriction that prevents your site\u2019s page to request any data(in our case HTML) from a remote site. Here is a wiki page<\/a> that explains this issue and possible workarounds<\/a><\/li>\n

    \"bag<\/p>\n

  • The (X)HTML page can appear like a bag full of garbage. I would suggest that you never parse HTML<\/a>…it will FAIL soon, and you will have to fix it which will FAIL again, its a vicious circle<\/li>\n

    HTML page is full of Garbage<\/span><\/h3>\n

    \"\"<\/p>\n

    So, let us assume somehow you get the page HTML<\/a> within your page through plain Javascript\/AJAX\/jQuery or any other way, then how your page will get the data it wants…<\/p>\n

    Well, most of the pages has similar construct:<\/p>\n

    <doctype....\n<html>\n<head>\n..\n..\n<script>..<\/script>\n.\n<\/head>\n<body ....>\n...\n..\n<<<<<Tags jungle>>>>\n..\n<some sweet tag> <3 Your Data <3 <\/some tag>\n..\n.<more tags>\n\n<\/body>\n<\/html><\/pre>\n
    What we will do is to load this page HTML into a javascript varible, then simply chop all the content section from the start up to  tag, also trim any <script>
    \ntags. Then we will run a wild replace using regular expression that will make any tag <* into <div tag<\/p>\n
    You can further continue this chopping and transformation of data to get closer to pure data. Once we have the HTML gone through the above process, we will have something that will look like this:<\/p>\n
    <div>\n<div>\n.\n.\n<\/div>\n<div>\n<div> <3 Your Data <3 <\/div>\n<div>\n..\n.<\/pre>\n
    which we will host(assign to innerHTML property) into an invisible div<\/span>, which will force the browser to parse and render the HTML and make this HTML part of your DOM object.<\/p>\n
    Later you can query this data, using something like…
    \nvar data = docuemnt.getElementById(\"someId\").innerText;<\/code><\/p>\n
    where someID is the parent element, containing required data.<\/p>\n
    Lets take an example of NewYork weather data page from AccuWeather.com:
    \nURL: http:\/\/www.accuweather.com\/us\/ny\/new-york\/10017\/city-weather-forecast.asp<\/code><\/strong><\/p>\n
    \"\"<\/p>\n
    if you inspect the page in IE developer tools, we will observe following:<\/p>\n
    \"\"<\/a><\/p>\n
    now assuming that you have managed to load this HTML into your page JavaScript,and its assigned to the src variable, thus src should look something like this:<\/p>\n
    \"\"<\/p>\n
    lets execute following JavaScript statements:<\/p>\n

    \nif(src === \"\")
    \nreturn;
    \nvar i = src.indexOf(\" \tsrc = src.substr(i);\t\t\/\/ chopped the Head part<\/code><\/p>\n
     <\/code><\/p>\n
     tag = src.replace(\/<[a-z]+\/gi,\"
    \ntag
    \nalert(tag);
    \n<\/code><\/p>\n
    this should give us the output as shown below:<\/p>\n
    \"\"<\/p>\n
    Further executing some more JavaScript statements provided below, we can reach to our data:
    \n
    \ndocument.getElementById(\"host\").innerHTML = tag;
    \ndata = $(\".info\").find(\".cond\").find(\".temp\")[0].innerText;<\/code><\/p>\n
    data = data.substr(0,3);
    \nalert(\"Today's Temp: \"+data);
    \n\/\/ host here is a div element
    \ndocument.getElementById(\"host\").innerHTML = \"Today's Temp: \"+data+\"\u00b0\";
    \n$(\"#host\").show();
    \n<\/code><\/p>\n
    Result will give us the temperature.<\/p>\n
    Here is the full source code:<\/p>\n
    download source code<\/a><\/p>\n
    \n<html\n<head>\n<title>Page rip demo<\/title>\n<script type=\"text\/javascript\" src=\"http:\/\/ajax.aspnetcdn.com\/ajax\/jQuery\/jquery-1.6.1.min.js\"><\/script>\n<\/head>\n<body>\n<script type=\"text\/javascript\" >\nvar url = \"weather.htm\";\nvar src = \"\";\nonload = function()\n\t\t{\n\t\t\t$.ajax({'url':url,'success':function(source)\t\t\t\t\t\t\t\t{\n\t\t\t\t\t\t\t\t{\tsrc = source;\n\t\t\t\t\t\t\t\t\talert(src);\n\t\t\t\t\t\t\t\t},\n\t\t\t\t\t\t\t\t'error':function(r,s,x)\n\t\t\t\t\t\t\t\t{\n\t\t\t\t\t\t\t\t\talert(\"Error while trying to get data :(\");\n\t\t\t\t\t\t\t\t}});\n\t\t}\n\nfunction GetTemperature()\n{\n\tif(src === \"\")\n\t\treturn;\n\n\tvar i = src.indexOf(\"<body\");\n\tsrc = src.substr(i);\t\t\/\/ chopped the Head part\n\n\ttag = src.replace(\/<[a-z]+\/gi,\"<div\");\n\talert(tag);\n\n\tdocument.getElementById(\"host\").innerHTML = tag;\n\tdata = $(\".info\").find(\".cond\").find(\".temp\")[0].innerText;\n\n\tdata = data.substr(0,3);\n\talert(\"Today's Temp: \"+data);\n\tdocument.getElementById(\"host\").innerHTML = \"<h2>Today's Temp: \"+data+\"\u00b0 C\";\n\t$(\"#host\").show();\n}\n<\/script>\n<input type=\"button\" onclick=\"GetTemperature()\" value=\"Show Temp\">\n\n<div id=\"host\" style=\"display:none;\"><\/div>\n<\/body>\n<\/html>\n<\/code><\/pre>\n
    Which will give us the following result:<\/p>\n
    \"\"<\/p>\n
    Pros: <\/strong>This approach is better than trying to parse the whole HTML yourself, which is more error prone and bound to fail frequently. Here we are letting the browser parse and include our HTML into the DOM, so we can run some simple JavaScript statements to get required data<\/p>\n
    Cons: <\/strong>this approach is way dirty itself and will fail someday, as soon as the page layout changes or somebody alters the source page HTML layout. Not to mention the browser compatibility as different browser treats things differently.<\/p>\n
    With the recent and continuing revolution going around on the web, things are getting easy with sites exposing their data through APIs or at least through Microdata\/Microformats<\/p>\n","protected":false},"excerpt":{"rendered":"
    You want to use some data that is provided by some site, but they doesn\u2019t expose any API to get that data. Well, a possible (and a very dirty) trick is to get the page HTML and rip data off it for our use. Not so easy dude… there are many hurdles: First one is […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[31,41,161,241,251,271],"tags":[],"_links":{"self":[{"href":"https:\/\/inullable.in\/blog\/index.php?rest_route=\/wp\/v2\/posts\/136"}],"collection":[{"href":"https:\/\/inullable.in\/blog\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/inullable.in\/blog\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/inullable.in\/blog\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/inullable.in\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=136"}],"version-history":[{"count":0,"href":"https:\/\/inullable.in\/blog\/index.php?rest_route=\/wp\/v2\/posts\/136\/revisions"}],"wp:attachment":[{"href":"https:\/\/inullable.in\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=136"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/inullable.in\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=136"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/inullable.in\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=136"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}