Web Server Updates – NET+OS 6.3

 

 

 

Last Updated: 06/22/07         Fix Count: 12

 

 

Title

Intermittent problems authenticating to mail servers

 

Case: 1231775 / 20959

 

Date Fixed: 06/22/07

 

Description

Server intermittently rejects connection attempt when using CRAM-MD5 authentication.

 

Solution

CRAM-MD5 digest calculation may contain NULL in the data field.  Code now handles this properly.

 

 

Title

Intermittent problems authenticating to mail servers

 

Case: 1228489 / 20959

 

Date Fixed: 06/08/07

 

Description

Server intermittently rejects connection attempt when using Digest-MD5 authentication.

 

Solution

Fixed a problem in the MD5 calculation function.  There was a strcat() using a string that was not properly initialized.

 

 

Title

Problems authenticating to mail servers using Digest-MD5

 

Case: 20959

 

Date Fixed: 02/19/07

 

Description

Server rejects connection attempt when using Digest-MD5 authentication.

 

Solution

Replaced local string variables with dynamically allocated pointers to prevent compiler from optimizing the Digest-MD5 calculation.

 

 

Title

Server header now customizable

 

Case: none

 

Date Fixed: 02/09/07

 

Description

Server header was not customizable by end user.

 

Solution

Made kServerHeader a variable so that customer can customize the server's header
 in the HTTP response header.  See the ApiReference for details.

 

 

Title

Browser authentication failure

 

Case: 1224523

 

Date Fixed: 02/02/07

 

Description

Browser fails to authenticate with ssl\web server if
SSL_CIPHER_LIST_ALL_DEFAULT is used.

 

Solution

Declare array that holds cipher list as a static array.

 

 

Title

Request too large error when posting data using Advanced Web Server 
 

Case: 19719

 

Date fixed: 11/06/06

 

Description

Posts larger than 4K bytes would generate a “Request too large” error.
The internal work buffer size was set at 4096 bytes.  
 

Solution

Added http_buffer_size in HS_SERVER_PARAMETER, and made kHttpWorkSize
variable instead of constant. This kHttpWorkSizeis used for POST data and its size may be
specified by the user. The fHttpWorkBuffer and fCurrentItemValue in the rpHttpRequest will be

allocated with the kHttpWorkSize size during initialization.

 

 

Title

Problem using kRpObjFlag_Disposition flag along with the Mozilla browser. 

 

Case: 1218061

 

Date Fixed:  9/28/06

 

Description

The filename is sent to the browser from the webserver as "/filename.xxx" instead of

"filename.xxx".  This causes the Mozilla browser to prompt the user to save the file

as "-filename.xxx".

 

Solution

Corrected problem with forward slash ('/') in URL response header.

 

 

Title

kMaxMimeTypeLength increased to allow additional header

 

Case: 18197

 

Date Fixed:  4/17/06

Description

Increased kMaxMimeTypeLength from 50 to 128.

Solution

This allows an extra header (such as Content-Disposition) to be added after the Content-Type header.

 

 

Title

Customer supplied error pages not displaying in AWS

 

Case:  18175

 

Date Fixed:  4/13/06

Description

When using the NAHSStartServer() routine and associated HS_SERVER_PARAMETERS struct the server is not utilizing the pages specified for sub-elements such as PageNotFoundErrorPage, AccessNotAllowedExceptionPage, etc.


Solution

Removed LENGTH_HS_SERVER_PARAMETER_VERSION_1_STRUCTURE.  This field was
preventing other fields in the structure from being updated with the customer's configuration.

 

Title

AWS thread priority can not be changed from default of 16.

 

Case: 1209985

 

Date Fixed:  3/29/06

Description

Priority of thread could not be changed.  It always runs at priority 16.

 

Solution

Fixed a bug the priority handling logic.  Now uses the default priority only if
priority is not specified.

 


Title

Realm security defective on the Basic Web Server

 

Case: 16482

 

Date Fixed: 07/01/05

 

Description

When a client enters a protected realm using the basic web

server, they are not being challenged.

 

Solution

Corrected the basic web server to properly recognize when a

page is a protected page and thus provide a challenge when needed.

 

 

Title

HTML 2 C Compiler Issue

 

Case: none

 

Date Fixed: 07/01/05

 

Description

When using the HTML 2 C compiler, the generated url.c file is not

formatted properly, thus when attempting to compile, the GNU compiler

throws an error saying the URLTable definition should be in braces.

Presently, the only way to get around this error is to manually enclose

each URLTableEntry entry line in braces; however further usage of the

HTML 2 C compiler results in unexpected behavior in the tool.

 

Solution

Updated the HTML 2 C compiler to include curly brackets for each

URLTableEntry instance within the URLTable, located in url.c.

 

 

Files:   netos\h\http_awsapi.h

            netos\h\rphttpd\AsExtern.h

            netos\lib\arm7\32b\ghs\libemailc.a

            netos\lib\arm7\32b\gnu\libemailc.a

            netos\lib\arm9\32b\ghs\libemailc.a

            netos\lib\arm9\32b\gnu\libemailc.a

            netos\lib\arm7\32b\ghs\libhttpd.a

            netos\lib\arm7\32b\gnu\libhttpd.a

            netos\lib\arm9\32b\ghs\libhttpd.a

            netos\lib\arm9\32b\gnu\libhttpd.a

            netos\lib\arm7\32b\ghs\librphttpd.a

            netos\lib\arm7\32b\gnu\librphttpd.a

            netos\lib\arm9\32b\ghs\librphttpd.a

            netos\lib\arm9\32b\gnu\librphttpd.a

            netos\src\examples\nahttp_pd\root.c

            netos\src\examples\nahttps\root.c

            netos\src\examples\nahttps_pd\root.c

 

Special Instructions

 

 

Patch Link:  WebServerUpdates_63

 

Dependencies

This patch also requires the installation of the following patch(es):

 

SSLUpdates_63

TCPIPUpdates_63

ACEUpdates_63

ApiReference_63