Re: [xml-dev] Cracking AJAX? Done yet?

["Peter Hunsberger" <peter.hunsberger@gmail.com>]

Not sure what you want to do, but you can mostly reverse engineer the
Ajax calls.  Sometimes the underlying libraries are obscured, but at
some level, every Ajax call begins with a Javascript invocation (plain
text) from a web page.

In our case, this makes it easier to get at the underlying data, once
you dig down far enough to figure out the calls you can invoke them
directly and get the relevant XML (or sometimes other wise encoded)
data directly.

There are tools to track the underlying HTML calls that work at the
browser level -- you shouldn't have to resort to proxies -- but so far
I've never had the need for them...

On 11/7/06, david.lyon@preisshare.net <david.lyon@preisshare.net> wrote:
> List,
>
> Since Ajax transfers xml data down the http pipe, is anybody aware of
> any http filters that can be used with ajax data to siphone the
> information out?
>
> For example, some website sells computer parts and they are using
> ajax. In the old days one would just screenscrape and parse the html
> to get to the data. Now with ajax it's all going up-and-down the html
> pipe and not being seen.
>
> The data should be there, somewhere hiding in the pipe somewhere.
>
> So from the website, if we just click at the right spots, and filter
> the http for xml tags, then we should get the data right?
>
> Maybe it can be done at the proxy server level?
>
> Just curious? has anybody tried?
>
>
> David
>
> _______________________________________________________________________
>
> XML-DEV is a publicly archived, unmoderated list hosted by OASIS
> to support XML implementation and development. To minimize
> spam in the archives, you must subscribe before posting.
>
> [Un]Subscribe/change address: http://www.oasis-open.org/mlmanage/
> Or unsubscribe: xml-dev-unsubscribe@lists.xml.org
> subscribe: xml-dev-subscribe@lists.xml.org
> List archive: http://lists.xml.org/archives/xml-dev/
> List Guidelines: http://www.oasis-open.org/maillists/guidelines.php
>
>


-- 
Peter Hunsberger