Post Reply

[XAP][Source] Webserver v0.5.5 (Bugfixes and prep work)

OP GoodDayToDie

8th July 2013, 03:10 AM   |  #1  
OP Recognized Developer
Flag Seattle
Thanks Meter: 2,707
 
5,725 posts
Join Date:Joined: Jan 2011
More
New, version Alpha 0.5.5, is now up on Codeplex and available for download here!
Wow, that took forever. Sorry about that! I spent a chunk of that time on vacation, but mostly I was doing a *lot* of behind-the-scenes hacking. The visible changes in this version aren't so great (and I can't promise I haven't introduced a regression or two, though I did try to test things) but this should unblock progress on other features I've wanted to add for ages.

In the meantime, this version fixes a number of issues: .REG download on all browsers should (hopefully!) now work, the server should hold fewer threads and connections open, the server should shut down faster (not a *huge* concern, I know, but it was an easy fix and it annoyed me how long you had to wait), IPv6 addresses are now both displayed properly in the link bar, and are also subordinate to IPv4 addresses; you'll only see a v6 if you don't have a v4 WiFi address at all. I've improved the error reports for various edge cases where the request parser fails; this probably won't matter (Ever seen an HTTP 505? Yeah, me neither). Page templates are slightly smaller, rely less on JS and more on HTML5, and (unfortunately) still render kind of awfully on mobile. One of these days...

Previous update (0.5.3): The major change this time is the addition of a button to download a registry key (including all its subkeys, and of course all their values) as a .REG file. Other changes include better handling of relative paths and path traversal in the file system, a "go up" link in the registry, and bugfixes on some of the more esoteric registry behaviors. Oh, and the ability to open the phone's web browser, pointing at the server, from within the app (the URL is now a link).

PLEASE REPORT ANY BUGS YOU FIND IN THE CURRENTLY IMPLEMENTED FEATURES, ESPECIALLY THE NEW ONES! I'll try to fix newly reported issues much faster this time!

I have added a support / Q&A thread here: http://forum.xda-developers.com/wind...hread-t2906882. Please use that thread to report questions; don't PM me unless it needs to be kept private for some reason!

KNOWN BUGS: Occasionally, the server closes the connection without actually returning the page first. I have no idea why; I spent hours tracing in the debugger and never caught it. Refreshing the page usually works, if that doesn't do it, just bounce the server.

ISSUES ON WP8.1:
  • You may be unable to run the app if you deploy it using "Application Deployment". Instead, deploy with "Windows Phone Application Deployment 8.1".
  • Problems have been reported in the past when the app is installed to the SD card. It's small, though; putting it on internal storage shouldn't be a problem.

IN CASE OF OTHER ISSUES: Please provide a *detailed* error report - what phone and OS version you have, what hacks you've installed, what Webserver version you're running, what you do to get the error to occur, and exactly *what* occurs - and I'll fix it as soon as I can!

I still plan to implement upload/write operations, hopefully soon! I'm also looking at moving the server to a background process and making the app just a control UI for it, adding support for authentication and/or HTTPS, adding some stylesheets to the web UI, adding cache and connection control, and much more.

As with the last few releases, the XAP is published twice; once as a fairly standard XAP that any phone can sideload, the second with many exotic capabilities to enable viewing of slightly more of the file system. The standard XAP has had its list of capabilities expanded to pretty much all of them that can be used without interop-unlock. The high-capability variant requires not just interop-unlock, but the additional capability-unlock hack available in the interop-unlock thread.

An item of note: the AllCapabilities version can open other drives in the file system. On phones with an SD card, it is mounted at D: and you can browse it as normal. Credit to @hjc4869 for this discovery!

Version 0.5.5 is mostly a ton of updates to the HttpServer code (currently its version number is at 0.4.1, vs. the old 0.3.7). Please see the BinaryServer branch in Git if you want to follow what I'm doing there and maybe try out bleeding-edge code (I can't really recommend it; I mean, I try not to check in broken code but it doesn't exactly get tested).

DESCRIPTION: This is a simple webserver app which can enumerate those files that are in folders readable from the sandbox, can download files, can browse the registry, and can display the contents of registry values of any type. It runs on WP8.x only. It is a spiritual successor to the Functional Webserver / WebServer (Mango) projects from WP7. This version is still missing a lot of functionality as I decided to implement it from scratch, but it is advancing swiftly. Note that there's no access controls implemented; use it on a public network only at your own risk!

Instructions are simple: sideload the XAP, connect to WiFi (required), run the app (called "WebServer Native Access"), point a web browser (on a PC or phone that is also on that local network) to the URL that the app displays. You should get a basic index page. Click on a Filesystem or Registry link to begin browsing the phone. There's a textbox near the top of all filesystem pages, type in a path there (for example, "windows" with no quotes) and hit Enter or click Get Files. You'll see a list of the contents of that folder. Click on a file to download it or a directory to open it. Navigating the registry is similar, except you'll need to specify the registry hive and then the path from that hive (or no path, to access the root of the hive).

Modifications (uploading or editing files, creating, deleting, or changing registry keys or values) are currently not supported. They will be "soon" although my personal testing suggests that basically the whole registry, and most of the file system, is off-limits for writing unless you use restricted capabilities. Interestingly, I can *read* most of the registry, including stuff that I probably shouldn't be able to.

You might see an error code (error 5 is "ACCESS_DENIED", you'll see it a lot). Or you might see a status 500 message because of an exception in the server. Or the server may just crash (hopefully not so often anymore...). I'm making it more resilient, but there are still bugs. Please report any previously-unreported issues you find, including how to reproduce them, and I'll fix them if possible.

Also feel free to request features or changes; I'll implement them if reasonably possible. The app is a mixture of C++ and C# code; I could probably have done it all in one or the other but wanted to have a C++ component in case I ran into something that wasn't available in C#, and although it probably would have saved some time, I decided that hacking up a web server in C++ was maybe not the best idea.

The source code is on Codeplex, at the following projects: https://wp8webserver.codeplex.com/ for the server and the app (C#) and https://wp8nativeaccess.codeplex.com/ for the native access wrappers (C++). You may have to fix up the reference paths to get the C# component to see the C++ component correctly. The code is reasonably well documented, but let me know if you have any questions. Permission to re-use the code or components is granted under the MS-PL (Microsoft Permissive License) as posted on Codeplex.

Go forth and find cool stuff!

Version history:
07 July 2013 - 0.2.0: Initial release, FS only, 920 downloads (source: 652 downloads)
14 July 2013 - 0.3.2: initial registry, HTTP server and web app encapsulation, source on Codeplex, 225 downloads
0.3.3: bugfixes, 454 downloads
0.4.2: basic registry values display, 86 downloads
0.4.3: bugfixes, 326 downloads
0.4.6: multistring registry values, bugfixes, updated libraries, first AllCapabilities version (950 downloads), 453 downloads
25 Oct 2013 - 0.4.8: binary and long registry values, formatting and bugfixes, 451 downloads AllCaps, 201 normal
22 Dec 2013 - 0.4.9: all registry value types, better threading, proper resume, remembers port, 97 downloads AllCaps, 53 normal
24 Dec 2013 - 0.5.0: background operation using Location APIs. Downloads: 1011 AllCaps, 963 Normal
20 Jul 2014 - 0.5.1: More capabilities, better navigation. Downloads: 108 AllCaps, 61 normal
07 Aug 2014 - 0.5.3: .REG export, better traversal, bugfixes. Downloads: 260 AllCaps, 164 normal
10 Oct 2014 - 0.5.5: Bugfixes and back-end work.

XDA:DevDB Information
WebServer Native Access, ROM for the Windows Phone 8 General

Contributors
GoodDayToDie

Version Information
Status: Alpha

Created 2014-10-17
Last Updated 2014-10-16
Last edited by GoodDayToDie; 15th October 2014 at 11:01 PM. Reason: Added link to Q&A thread
The Following 24 Users Say Thank You to GoodDayToDie For This Useful Post: [ View ]
8th July 2013, 03:10 AM   |  #2  
OP Recognized Developer
Flag Seattle
Thanks Meter: 2,707
 
5,725 posts
Join Date:Joined: Jan 2011
More
I'm going to use this space to mention something that's pretty cool:
J. Arturo of http://www.komodosoft.net is using a modified version of the HTTP server that powers this app in the ShareFolder app (http://www.windowsphone.com/s?appid=...a-8a2933a8bdb4) to support opening video files directly from Windows network shares! This was done to work around a limitation of the WP8 media control: it can only source from an isolated storage file or a HTTP URL. By running a server in the background and streaming the video file through it, and pointing the video player control at the localhost URL, it becomes possible to play the file on the phone without first copying it to the app's isolated storage. A very cool way to solve the problem! Also, reviewing the changes that were made to the network code of the server pointed me toward those threading fixes I made that have hopefully much improved version 0.4.9.
Please note that the updated version of ShareFolder with this feature may not yet be available, although it should be soon. It is a commercial (paid) app, but the author sought and received permission to use my code (although the license does not require such permission be received).
Last edited by GoodDayToDie; 22nd December 2013 at 11:16 AM.
The Following 4 Users Say Thank You to GoodDayToDie For This Useful Post: [ View ]
8th July 2013, 02:18 PM   |  #3  
Senior Member
Thanks Meter: 216
 
877 posts
Join Date:Joined: May 2012
What exactly is the problem with sockets? I am battling myself with sockets atm too, maybe we can share knowledge?
8th July 2013, 05:20 PM   |  #4  
OP Recognized Developer
Flag Seattle
Thanks Meter: 2,707
 
5,725 posts
Join Date:Joined: Jan 2011
More
Strictly speaking, the problem was with the phone's limited subset of the Sockets API forcing me to access it through functions I wouldn't normally use (asynchronous everything, SocketAsyncEventArgs and lambdas and AutoResetEvents and so on everywhere...) but I've got a pretty good handle on it now, at least for the System.Net.Sockets.Socket and its friends. The new .NET 4.x ones (using the async keyword and all) are in a different namespace; I didn't mess with them. They are more abstracted from the Bekeley sockets interface that I'm used to from C, but they are also (supposedly) more user-friendly, especially if you don't feel like writing all your own thread management code (and in fairness, I should re-write the webserver's threading to use threadpools; they're better for this type of work).

If you want to ask questions about the topic, I suggest starting a new thread (possibly in the Q&A subforum, although it's also dev related...) and I'll answer if I can.
The Following User Says Thank You to GoodDayToDie For This Useful Post: [ View ]
8th July 2013, 08:51 PM   |  #5  
Recognized Developer
Flag Boston, MA
Thanks Meter: 426
 
1,493 posts
Join Date:Joined: Nov 2009
Donate to Me
More
GoodDayToDie, just an idea: how about sharing your source code via CodePlex or GitHub?
The Following 2 Users Say Thank You to sensboston For This Useful Post: [ View ]
9th July 2013, 06:58 PM   |  #6  
snickler's Avatar
Forum Moderator / Recognized Developer
Flag Wheeling, WV
Thanks Meter: 499
 
850 posts
Join Date:Joined: Aug 2010
Donate to Me
More
Oh man, this is pretty nice! GoodDayToDie does it again!
9th July 2013, 07:07 PM   |  #7  
snickler's Avatar
Forum Moderator / Recognized Developer
Flag Wheeling, WV
Thanks Meter: 499
 
850 posts
Join Date:Joined: Aug 2010
Donate to Me
More
So far, I can read \Windows, the current install folder which you access just by typing "." with no quotes and the current application folder by typing ".." I can access the .dlls, .winmd and AppManifest.xml from the current install, but from everywhere else, it goes boom. This is a great step towards something awesome though!

EDIT:

I was wrong. For some reason, when you click on a folder it's trying to "download" it, rather than chdir. I can get pretty far into the Windows directory.

THAT's what you meant by "Click on a file (note: there's no current way to tell the difference between files and folders) to download it.

You might see an error code (error 5 is "ACCESS_DENIED", you'll see it a lot). Or you might see a status 500 message because of an exception in the server. It's getting a lot more resilient but there are surely still some bugs. ".


If you see a folder, just type the full path to it instead of clicking on it and you will be able to read the contents.

ANOTHER EDIT:

I just found a file inside of the \Windows\System32 directory named [guid].devicemetadata-ms (It's easier to just search for "devicemetadata-ms"). It's a cab file with some metadata about WP8 with a sign.cat and packagesign.cat file in the archive. I don't know what these files could potentially be useful for.
Last edited by snickler; 9th July 2013 at 07:22 PM.
9th July 2013, 07:26 PM   |  #8  
OP Recognized Developer
Flag Seattle
Thanks Meter: 2,707
 
5,725 posts
Join Date:Joined: Jan 2011
More
New version in a day or two (busy tonight). Features I plan to implement (not necessarily in the next version or at any particular time):
File upload (IsoStore and, of all crazy things, install directory are writable. I think I'll put a flag on each FS page that says whether the current dir is writable...).
File deletion (where possible, of course).
File and Directory distinction in the listing (clicking a dir should open it, not error out).
Filesystem index page with links to folders that can be accessed successfully (since the root isn't readable).
Some more file info (size, probably attributes, possibly permissions).
Possibly an option to preview a file (as plain text) without downloading it.
Some kind of background mode (the server uses minimal resources when not actively servicing a request, so I'll see if I can get it to work in the background, perhaps by abusing the music transfer agent...)
Some kind of offline mode (at least basic file browsing within the app, as an alternative to using the web interface, though I might just make a second app for that).
Source code changes: separate the server code from the webapp / phone app code (move it into its own project).
Source code changes: move to a hosted version control service, probably CodePlex (good suggestion sensboston).
Maybe add an icon and such...

Any other suggestions?

I also want to try experimenting with various non-standard capabilities and see if I can get access to more of the system . I've already added the ability to access removable storage, but I've also found a bunch of really weird and frequently undocumented capabilities in the OS's policy configuration files, and I need to look into those... The interesting (and possibly the uninteresting) ones are probably blocked for unsigned sideloaded apps, but it's worth checking on anyhow.
Last edited by GoodDayToDie; 9th July 2013 at 07:39 PM.
The Following User Says Thank You to GoodDayToDie For This Useful Post: [ View ]
9th July 2013, 07:33 PM   |  #9  
OP Recognized Developer
Flag Seattle
Thanks Meter: 2,707
 
5,725 posts
Join Date:Joined: Jan 2011
More
Yeah sorry, I should have been more explicit about clicking on dirs. not working in 0.2.0. Also, it's "unofficial" but if you check the URL bar you'll see a URL parameter called something like "pattern" (by default, it's *) and if you change that, you can filter the results. For example, "foo*.exe" (note: no quotes!) will search for EXE files whose names start with "foo". Among other uses, this makes it a lot faster to load large dirs like System32. This will be added to the UI at some point. Also note that URL decoding is applied correctly to querystring parameters (Probably already noticed with the path sometimes written using %5C for \) so you can add special characters that way if needed, though currently any of them but \ will probably just cause an exception.
...
Actually, does this filesystem support Alternate Data Streams? If so, you should be able to download them by appending a : and the ADS name to the filename in the download URL...
The Following 2 Users Say Thank You to GoodDayToDie For This Useful Post: [ View ]
15th July 2013, 12:52 AM   |  #10  
OP Recognized Developer
Flag Seattle
Thanks Meter: 2,707
 
5,725 posts
Join Date:Joined: Jan 2011
More
OK, so that was a new version in five days. Sorry, stuff takes time.
The source code is now on Codeplex. The native access portion is at https://wp8nativeaccess.codeplex.com/, and the web server portion is at https://wp8webserver.codeplex.com/. Both are licensed MS-PL and use Git for version control. The full XAP is also available for download from the Webserver project on Codeplex.

The Following 2 Users Say Thank You to GoodDayToDie For This Useful Post: [ View ]
Post Reply Subscribe to Thread

Tags
webserver, xap
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes


Top Threads in Windows Phone 8 Development and Hacking by ThreadRank