Accessing Pages Programatically

I am developing a personal application that requires pulling data from the HTML pages. When the user presses a button the application will log in, parse for information, and report back. I have successfully logged in programatically. I am having issues actually reaching the data pages, though.

The URL fragments (i.e. #/Towns/Castle) are whats tripping me up. Can anyone help me with how to access these fragment pages from within Java code? The following code example returns a "Resource not found" response.

        String url2 = URLEncoder.encode("#");
        HttpPost httppost = new HttpPost("http://elgea.illyriad.co.uk/"+url2+"/Town/Castle");
        CookieSpecBase cookieSpecBase = new BrowserCompatSpec();
        List<Header> cookieHeader = cookieSpecBase.formatCookies(cookies);
        httppost.setHeader(cookieHeader.get(0));
        HttpResponse response;

        try {
            response = client.execute(httppost);
        } catch( Exception e) {}

Edit: The personal application will be made public after a potential future release from the developers, since it is against policy to request for Uname and Pwd.


Edited by matiez - 20 Jan 2012 at 18:10

Perhaps I can do so!

Thank you for the clarification, GM Stormcrow. I will cease attempting to access information in this manner. I am highly interested in the player-revokable XML feed. I will prepare a sample XML data file that will fit my needs.

Edit: GM Stormcrow: I have an XML schema and example file for your review. Where would you like me to send them?


Edited by matiez - 24 Jan 2012 at 17:12

sounds like the XML feed might do something like that, muykul.  But I'm not an expert.

Muykul wrote: I agree that an XML feed would be the way to go as it wouldn't include the "overhead" (graphics, css, javascript etc...) of the full rendered HTML version. I wonder if matiez every got his schema to the devs? Half the battle is just finding an acceptable way to get the information from the webserver to the device without violating the T&C. After that is done, writing the app should be relatively trivial / easily upgraded later. My thinking is along the lines of: Verify writing an app is possible under the T&C Determine which data should be downloaded. Determine the authentication mechanism. Determine the exchange method (XMl, API etc...) Verify data exchange functionality Write/test the application I'm encouraged because the Devs have stated in other posts that they are willing to do this sort of work, however I understand they are fighting a battle against unscrupulous individuals who would try and "farm" the game for money. -Muykul