uwekeim / aspnetserve Goto Github PK

The current simple UI for the server should remain as-is. It provides a
clutter free illustration of how to create a functional server, and it is
easy to use in a hurry.

However, for more advance server features a more advanced server will be
needed. Therefore I propose adding a Windows service backed server that can
be configured via XML. This initial feature will not provide a UI for
configuring the server, instead the XML will need to be manually edited.
Future feature requests will build a UI.

This should be classified under "enhancement" -- I would like to see some 
way of packaging an entire asp.net web application into a single file.

If you're familiar w/ java web applications, you can package them into a 
WAR (web archive) and then deploy that to the java web server. You can 
essentially accomplish the same thing you're doing here by using a 
container such as jetty and using a WAR.

I was hoping there would be a way of packaging an entire web application 
into a file like a WAR. Perhaps a zip file w/ no compression?

That way, I don't have to distribute or make my files easily available to 
the casual observer. IOW, I don't want people poking around my embedded 
asp.net pages. Plus it's much, much easier to package into an install if I 
don't have to worry about 500 files.

Any thoughts?

Name based virtual hosting support would be nice.

More about it can be found @ http://en.wikipedia.org/wiki/Virtual_hosting

Currently aspNETserve.Core must be registered in the GAC before the server
can start. This is due to the use of the CreateObject method on the
System.Web.Hosting.ApplicationManager object to create the
aspNETserve.Core.DomainHook object in the hosted AppDomain.

Perhaps another implementation can be found that removes the need to
install any components in the GAC.

What steps will reproduce the problem?
1. Create .NET 4.0 project.
2. Attempt to host in aspnetserve
3. Not ASP.NET failure on targetFramework element.

What is the expected output? What do you see instead?
Would love to see .NET 4.0 supported.

Why not just build a asp.net module for http://www.codeplex.com/webserver?

Then you get http authentication, ssl and keep-alive connections..

aspNETserve (or at least the simple UI) is broken under Windows XP in at 
least the following configuration:

aspNETserve versions 1.2, 1.2.1, and 1.3.0
Windows XP SP2
.NET 2.0 SP1

The application opens a TCP/IP port (as indicated by Windows Firewall), but 
is non responsive to requests. I have verified (as best I can) that the 
firewall is not blocking the communications.

This issue does not affect Windows Vista.

Hi,

I installed aspnetserve version 1.3.0.0 and tried simply to serve a folder
with image files with different sizes. Aspnetserve was started from the
Windows Explorer context menu.

Files bigger than about 200K return an empty response, smaller are
downloaded or shown normally in the web browser.

I tested on two machines: WinXP SP2 and W2K3 Server, with Firefox 2.0 and
IE6, with same results.

The GetProtocol() method of AspNetWorker is not implemented by indirection
of the IsSecure() method of the same class. 

Somehow figure out how to implement the IsSecure method to make the
GetProtocol() method work.

For "Web Applications" aspNETserve has limited support, requiring the
application to be published to a directory before it can be hosted in
aspNETserve.

NOTE: This issue does not effect "Web Site" projects.

For more information about "Web Site" vs "Web Application" projects see:
http://msdn2.microsoft.com/en-us/asp.net/aa336618.aspx

It would be nice if the aspNETserve server supported authentication similar
to IIS. 

For more information on how IIS authentication works please refer to:
http://windowsitpro.com/web/article/articleid/15843/iis-101-the-basics-of-iis-au
thentication.html

Just a minor defect: In version 1.3.1 the 
WebApplicationPackage.ExtractWapToPath(path) method won't extract zipfiles 
(correctly).
At the first line, "new ZipFile(_stream)" should be "ZipFile.Read
(_stream)". ZipFile's ctor expects an output stream but an input stream 
was given.

HTTP persistent connections are currently unsupported by aspNETserve.

More on persistent connections in HTTP can be read at:
http://en.wikipedia.org/wiki/HTTP_persistent_connections

Add HTTPS support to aspNETserve.

What steps will reproduce the problem?
1. Use IE to open cnn.com, abcnews.com, and slate.com.
2. Save page as "Webpage, complete: html" into a folder where aspnetserv 
can serve pages from.
3. Open those pages through aspnetserv.

What is the expected output? What do you see instead?
Pages are expected to render similar to the original pages.
Aspnetserv is having problems with images.
msn.com seems to work but not cnn.com, or abcnews.com.

What version of the product are you using? On what operating system?
Software version is 1.3.1.0 on Windows 7 Ultimate.

Please provide any additional information below.

aspNETserve currently has no way to specify MIME types for static (non
ASP.NET) content. It would be nice if there was some way to map MIME types
to file extensions, or something.