W3Mfc v1.11

Download source files - 34 Kb

Introduction

Welcome to W3Mfc, a collection of freeware MFC classes to implement a simple Web server.

The idea behind is W3Mfc was originally to learn about the Http protocol and how it is implemented on Win32. It is not intended to be a replacement for IIS or Apache. Instead it is designed as a tool for learning or in cases where deployment of a solution on IIS would be considered overkill or your product must run on 95/98 in addition to NT.

For detailed information about the HyperText Transfer Protocol you should read RFC 1945, You can download this from a number of sites by searching for RFC and 1945 on www.yahoo.com.

Another document that these classes refer to is RFC 2045 which defines MIME.

The classes which constitute W3Mfc are:

CHttpServerSettings:

This class contains the settings which are used to configure the web server. Example member variables in this class include the virtual directories and the their default filenames. If you are developing a stand alone web server based on W3Mfc, you could for example store all the variables for the CHttpServerSettings instance in an ini file or in the registry.

CHttpServer:

This is the actual class which implements the web server. It has a number of very simple functions to allow you to control the state of the web server such as Start and Stop. Internally a background thread is spun off to handle the client connections.

CHttpSocket:

This is a simple C++/MFC encapsulation of an SDK socket.

CHttpResponseHeader:

This class helps in the handling of sending request headers when returning the HTTP responses to clients. It provides a number of methods to allow standard Http headers to be added to the client response.

CHttpMimeManager:

This class is used when returning client responses. It is used to determine to mime type of a file given its extension type. This information is taken from the registry and is cached in this class. For example files of .htm or .html will normally be of mime type "text/html".

CHttpRequest:

This class represents a request from a client. It contains information such as the URI of the request, the Http Verb used and the Http version used for the request. A member of this type is stored in the CHttpClient class.

CHttpClient:

This class is used in the CHttpServer class to handle client connections. It handles the parsing of client requests and returning the appropriate response. A number of virtual functions are provided to allow end user customisation.

Features

Usage

History

To Do

Contacting the Author

Features

• HTTP/1.0 compliant.
• Uses the Windows registry to determine mime type thus simplifying configuration.
• Supports passthrough plaintext authentication for files located on NTFS volumes.
• Supports running under a configurable user account.
• Supports binding to a specific IP address.
• Supports multiple virtual directories.
• Supports directory listing.
• Server name returned can be easily configured.
• Supports server redirection by means of the HTTP 301 status code.
• Consumes very little system memory and CPU resources.
• Compact and easy to follow implementation.
• The interface provided is synchronous which provides an easier programming model than using asynchronous sockets.
• The code does not rely on the MFC socket classes. These classes have a number of shortcomings, one of which causes problems when they are used in NT services.
• The code can be used in a console application without any problems.
• The classes are fully Unicode compliant and include Unicode built options in the workspace file.

Usage

• To use the class in your code the following modules in your project:
  • base64.cpp/h
  • HttpClient.cpp/h
  • HttpMimeManager.cpp/h
  • HttpResponseHeader.cpp/h
  • HttpSocket.cpp/h
  • W3Mfc.cpp/h
  You will also need to copy over all the resources from the w3mfc.rc file into your resource file.
• Your code will need to include MFC either statically or dynamically.
• You will need to have a functioning winsock stack installed and correctly initialised prior to starting the web server. Depending on your application, this will involve calling either WSAStartup() or AfxSocketInit() at startup of your application.
• You will also need to have afxtempl.h ,winsock.h or afxsock.h and afxpriv.h in your precompiled header. The code will work just aswell in a GUI or console app. The code should also work in a multithreaded application, although it has not be explicitly tested in this scenario.
• To see the class in action, have a look at the code in InitInstance() in the module main.cpp on how to start up and stop the server.

History

V1.0 (4th May 1999)

• Initial public release.

V1.1 (29th June 1999)

• Implemented support for "HEAD" command.
• Sample provided now also displays the HTTP verb used.
• Sample provided now also displays the date and time of each request.
• Now fully supports multiple virtual directories.
• Now fully supports URL's with encoded characters.
• Implemented support for "DELETE" command.
• Now returns an "Allow:" HTTP header.
• Timeout for requests is now 90 seconds if built for debug.
• Now supports directory listing.
• User name is now displayed in the log window.

V1.11 (29th February 2000)

• Fixed a number of VC 6 level 4 warnings.
• Now empties any passwords transmitted once they are used.
• Now implements W3C Common Logfile logging to the console window.

To Do

GENERAL:

• Support for CGI.
• Support for ISAPI.
• Support for NSAPI.
• HTTP/1.1 support.
• TransmitFile support.
• Integrated search tool.
• Support for NCSA and Apache Server Side Includes (SSI).
• Multithreading / thread pool support to improve performance.

SECURITY:

• Support for SSL.
• NT authentication.
• PCT support.
• Integrated Certificate manager.

LOGGING:

• Support Apache compatible common logfile format log files.
• W3C extended log format.
• Log to ODBC database.
• Daily log files.
• Log file cycling.
• Log file archiving.
• Customizable log file formats.
• Real-time performance counters.
• NT Event Log logging

Contacting the Author

PJ Naughter
Email: pjn@indigo.ie
Web: http://www.naughter.com
29 February 2000

You must Sign In to use this message board.

FAQ    Noise Tolerance Very HighHighMediumLowVery Low   Layout Expand Posts & RepliesThread ViewNo JavascriptNo JS + Preview   Per page 102550

Msgs 1 to 21 of 21 (Total in Forum: 21) (Refresh) FirstPrevNext

Obtaining MIME type for unregistered file types using FindMimeFromData() ejg123 14:41 10 Nov '08   FYI- Microsoft provides FindMimeFromData(), a quasi-documented function for determining the MIME type by inspecting the first 256 bytes of file data. If you really need an accurate MIME type, you might want to try it when the registry lookup comes back empty. I was surprised at the number of common file types that are not documented, e.g. on our Windows 2003 server ".doc" was not included in the registry. Apparently IE uses this function, as I came across it when investigating why the values returned through registry lookup did not match those generated via IE. HTH, Eric Gilbertson PSS Systems Sign In·View Thread·PermaLink Read Response optimisize thomasCAE 11:48 13 Feb '07   Hi, what do you think about the following optimisation, which is very usefull if thinking about uploading large files by a post command to the webserver. Change ReadResponse(...) { ... if ((nBufRemaining-nData) == 0) //No space left in the current buffer { //Allocate the new receive buffer nBufSize += nGrowBy; //Grow the buffer by the specified amount LPBYTE pNewBuf = new BYTE[nBufSize]; //copy the old contents over to the new buffer and assign //the new buffer to the local variable used for retreiving //from the socket memcpy(pNewBuf, request.m_pRawRequest, request.m_dwRawRequestSize); delete [] request.m_pRawRequest; request.m_pRawRequest = pNewBuf; } ... } to ReadResponse(...) { ... if ((nBufRemaining-nData) == 0) //No space left in the current buffer { //Allocate the new receive buffer if ((nContentLength != -1) && (nContentLength > nGrowBy)) { if (nContentLength < 10 * 1024 * 1024) //avoid to big blocks if wrong content length nBufSize += nContentLength; else nBuffSize += nGrowBy } else nBufSize += nGrowBy; //Grow the buffer by the specified amount LPBYTE pNewBuf = new BYTE[nBufSize]; //copy the old contents over to the new buffer and assign //the new buffer to the local variable used for retreiving //from the socket memcpy(pNewBuf, request.m_pRawRequest, request.m_dwRawRequestSize); delete [] request.m_pRawRequest; request.m_pRawRequest = pNewBuf; } ... } This will decrease upload time for a 6MB File from 25 seconds to 2 seconds, by avoiding heavy usage of new allocation and copy of memory. Sign In·View Thread·PermaLink 2.00/5 (1 vote) Bug in Transmit Directory thomasCAE 3:13 16 Nov '05   The following bug prevents you from serving directory with spaces inside after this small modification it works very well: In CHttpDirectory::TransmitDirectory change sLine.Format(_T("<tr>\r\n<td><a href=\%s\>... to sLine.Format(_T("<tr>\r\n<td><a href=\"%s\">... Regarding the two " encapsulating the %s. By the way this is more W3c conform. But PJ good job. Go on... Sign In·View Thread·PermaLink Bug in CThreadPoolServer thomasCAE 3:01 16 Nov '05   A bug in the CThreadPoolServer class crashes your application if using extension dlls. The original typedef of the function pointer for CreateWaitableTime and SetWaitableTimer missing the calling convention. Think you are lucky if you do not run in the same bug using the original source by including cpp and h files. The correct version must be typedef HANDLE (WINAPI *lpfnCreateWaitableTimer)(LPSECURITY_ATTRIBUTES, BOOL, LPCTSTR); typedef BOOL (WINAPI *lpfnSetWaitableTimer)(HANDLE, const LARGE_INTEGER*, LONG, PTIMERAPCROUTINE, LPVOID, BOOL); in CThreadPoolServer class. Sign In·View Thread·PermaLink Bug HttpCGI.cpp of W3Mfc 1.72 Gregoire 7:08 9 Oct '05   I think that there is a bug in CHttpCGI::ReadFromClientStdout of HttpCGI.cpp of W3Mfc 1.72. The problem lies when the CGI output is very big. The output is the following: HTTP/1.0 200 OK datadatadatadatadatadataHTTP/1.0 200 OK datadatadatadatadatadatadatadatadataHTTP/1.0 200 OK and so on In other words, some HTTP/1.0 200 OK are sent in the middle of the transaction. Here is the fix: In CHttpCGI::ReadFromClientStdout 1. Remove: bFirstBuffer = FALSE; 2. Replace twice: if (!bFoundHTTPReturnCodeLine) by: if (!bFoundHTTPReturnCodeLine && bFirstBuffer) 3. - Add at the end of the while loop bFirstBuffer = FALSE; The while loop then becomes: while (bMore) { DWORD dwRead; if (!ReadFile(hChildStdout, pszBuf, pSettings->m_dwCGIResponseBufferSize-1, &dwRead, NULL) || dwRead == 0) bMore = FALSE; else { //Used as a return value to indicate how much was sent to the client dwDataSent += dwRead; BOOL bFoundHTTPReturnCodeLine = FALSE; if (bFirstBuffer) { //NULL terminate the data (so that we can use strstr) pszBuf[dwRead] = '\0'; //See if the "Connection: Keep Alive" is being transmitted bFoundKeepAlive = (strstr(pszBuf, "Connection: Keep-Alive") != NULL); if (bFoundKeepAlive) { //Note it is important that "Content-Length" be also sent when using keep alives //as otherwise client browsers do not know when to stop reading to get the end //of the first response bFoundKeepAlive = (strstr(pszBuf, "Content-Length: ") != NULL); } //Do we have a HTTP return code line bFoundHTTPReturnCodeLine = (strstr(pszBuf,"HTTP/") != NULL); //We only do this parse on the first buffer } //Send the data back down the socket try { char* pszTTPReturnCodeLine = "HTTP/1.0 200 OK\n"; #ifdef W3MFC_SSL_SUPPORT if (!bFoundHTTPReturnCodeLine && bFirstBuffer) pClient->m_Socket.SendWithRetry(pszTTPReturnCodeLine, strlen(pszTTPReturnCodeLine), pSettings->m_dwWritableTimeout, pClient->m_SSL); pClient->m_Socket.SendWithRetry(pszBuf, dwRead, pSettings->m_dwWritableTimeout, pClient->m_SSL); #else if (!bFoundHTTPReturnCodeLine && bFirstBuffer) pClient->m_Socket.SendWithRetry(pszTTPReturnCodeLine, strlen(pszTTPReturnCodeLine), pSettings->m_dwWritableTimeout); pClient->m_Socket.SendWithRetry(pszBuf, dwRead, pSettings->m_dwWritableTimeout); #endif } catch(CWSocketException* pEx) { //Report the error CString sError; sError.Format(_T("CHttpCGI::ReadFromClientStdout, Failed to send to socket, Error:%d"), pEx->m_nError); pClient->m_pServer->OnError(sError); pEx->Delete(); bMore = FALSE; } } bFirstBuffer = FALSE; } Gregoire Sign In·View Thread·PermaLink 2.00/5 (2 votes) ISAPIMap rgordon99 19:10 22 Sep '03   Hello PJ, Great job. Fast question, how do you use the ISAPIMap ini settings. Looking through the source I can tell that it's something like ext=???, the ext being the file extension but I'm not sure what you are looking for it to be equal to. Also, to make an MFC extension do I set the defines: W3MFC_EXT_CLASS, THRDPOOL_EXT_CLASS and SOCKMFC_EXT_CLASS to __declspec(dllexport) p.s. Keep the Observatory progress pics coming, the're great. Thanks Rick Gordon Sign In·View Thread·PermaLink Re: ISAPIMap pjnaughter 0:12 23 Sep '03   ISAPIMap: Just create a section of the form: [ISAPIMap] .someext=c:\somedirectory\isapidll1.dll .someext=c:\anotherdir\isapidll2.dll Note this is not required if you will be using the ISAPI dll path directly in a URL. MFC Extension: See MFC Technote 33 on how to export functions from a DLL. This also points out the problems that AFX_EXT_CLASS has. This is the reason why I use my own defines. Observatory pics: More on the way today or tomorrow!! Sign In·View Thread·PermaLink RFC 2045 Chester Lu 12:18 22 Sep '03   How do I found RFC 2045 document in codeproject.com? Thansk. Sign In·View Thread·PermaLink Re: RFC 2045 pjnaughter 13:17 22 Sep '03   As outlined in the documentation which I supply with the code, just use any search engine using the words RFC and 2045. For example http://www.ietf.org/rfc/rfc2045.txt Sign In·View Thread·PermaLink Working minimized PatrickL 20:30 12 Aug '03   1st of all, thanks very PJ, much for your contributions ! Great quality ! I downloaded your latest VFWGrab 1.05 from you Web site, build it, works fine. Now if I minimize the main window, the picture stays the same... (I use IncrementFilename and PeriodicInterval) When I Maximize, pictures are updated again. Is it a WebCam driver problem ? Can I force an acquisition when minimized ? Thanks for the help ! Patrick Sign In·View Thread·PermaLink Re: Working minimized pjnaughter 23:46 12 Aug '03   Could be a webcam driver problem but I'd suspect it is an interaction with how user32 draws minimized windows, If you think about it there is no need to update the client area of a window which is minimized. A few ideas, play around with the OnPaint handler and DefWindowProc to see if you can fool it into drawing, otherwise I'd suggest you modify the code to hide the window or something like that rather than allow it to be minimized (at least when you want to capture). Another idea to avoid this problem would be to look into DirectShow which I'd be pretty confident does not have this problem as it is not based on use a HWND!. Sign In·View Thread·PermaLink Re: Found a solution ! PatrickL 10:33 13 Aug '03   He PJ Thanks for the directions ! I tried OnPaint, then OnCmdMsg .. just to find that I was notified anyway for every update request ! Then I looked at your code, and found there, an easy solution: void CMainFrame::OnFileCapture() { // kick the webcam in case it needs it // the main window could be minimized, // or the screen saver be turned on.... BOOL ok = m_wndCap.GrabFrame(); Et voila ! Cheers Patrick Sign In·View Thread·PermaLink what is the difference between http 1.0 & http1.1 mathieu ruellan 23:27 10 Dec '02   has anybody implemented http 1.1 functionality??? thx Sign In·View Thread·PermaLink Re: what is the difference between http 1.0 & http1.1 R. Reyes 2:46 21 Feb '03   The 2 main features of HTTP/1.1 over 1.0 are just: - Virtual hosting using the HOST header, i.e. having more than 1 domain managed on a single computer. This is the main reason all the web servers are 1.1 compliant, and why today a HTTP/1.0 browser can hardly browse more than 1% of the web. - The Keep-Alive feature allows a client and a server to process several requests with one single socket connection. Really worth it, when you know that a single web page often means tens of http requests. Sign In·View Thread·PermaLink Latest version. Brian Delahunty 6:38 19 Jun '02   Just downloaded the latest version. Thanks PJ "When a friend hurts us, we should write it down in the sand, where the winds of forgiveness get in charge of erasing it away, and when something great happens, we should engrave it in the stone of the memory of the heart, where no wind can erase it" Nish on life [methinks] "It's The Soapbox; topics are optional" Shog 9 Sign In·View Thread·PermaLink 2.00/5 (3 votes) Great Job slashp 11:32 11 Jun '02   You always do great classes thx Sign In·View Thread·PermaLink How to start it? -= Matt Newman =- 14:55 1 Nov '01   I compiled it and can't seem to get it to work. It just says web server is starting. Am I doing something wrong? I am running Windows XP on NTFS with the Unicode version. -Matt Newman -Matt Newman Sign In·View Thread·PermaLink 1.00/5 (1 vote) Re: How to start it? P J Naughter 0:48 1 Feb '02   First make sure you have the latest version from my web site at www.naughter.com Sign In·View Thread·PermaLink 1.67/5 (3 votes) A BUG!! Varun Shoor 6:25 16 Jun '00   well i found a bug you cant download two files simultaneously with this server try downloading 2 big files off your computer and you will know what i mean. i think the reason is non threading of the function called TransmitFile in CHttpClient please update the source code or email me a way to cure this thing i would be ver gratefull Varun Shoor plotoders@yahoo.co Sign In·View Thread·PermaLink 2.00/5 (1 vote) Re: A BUG!! P J Naughter 0:49 1 Feb '02   The latest version on my web site implement an IOCP based thread pool so no more probs like the one you reported. Sign In·View Thread·PermaLink 1.75/5 (4 votes) http://localhost:90/.... Masaaki Onishi 18:11 8 Jun '00   Hi, Codegurus around the world. Since I'm looking for the web server source code, I so appriciate for this code. If someone want to take a test of your html, we can use W3MFC. To do this, 1) Change the connection setting to LAN in Internet options. (IE) 2) Type http://localhost:90 or http://localhost:90/index.html or htm (if you use port number as 90 in the source code.) Generally speaking, we use 8080. 80 is a default port of the web server. I often use FrontPage98's tiny web server, but now I got my toy to the web stuff. Have a nice day. -Masaaki Onishi Sign In·View Thread·PermaLink 3.50/5 (2 votes)

Last Visit: 6:51 8 Nov '09     Last Update: 6:51 8 Nov '09 1