There have been 2 issues identified when using WebStar 5 on OS X. We are working with 4D to resolve these issues which are only exposed when pages > 32 K in size are passed back to the WebStar engine via the WSAPI.
When >32K of page data is passed back to WebStar from the WitangoWebstar.so plug-in, Webstar chunks the data before sending it to the users browser. During this process, the HTTP Staus Code and HTTP Reason Phrase which the WitangoWebStar.so plug-in passes back are dropped as well as character 10240 in the page data (10 x 1024 bytes). If you see a character(s) missing from your page and you are using WebStar, check to see if it is character 10240 or a multiple of. Thanks to Joe (the missing Char) and Roland (corrupt http header) for their patience in helping to isolate these bugs as I dragged them through the workings of http, etc. 4D is now investigating the issues we have reported to them. Phil On 3/4/03 11:13 AM, "Roland Dumas" <[EMAIL PROTECTED]> wrote: > My issues on Xserve were identified and addressed. No Xserve related > issues at all; just a confluence of conditions that prevented getting > off the ground. > > On Monday, March 31, 2003, at 08:33 PM, Christian Platt wrote: > >> There seem to be some doubts about using xserve in the list. >> >> What i can confirm... >> >> Witango Server works on MacOS X Server 10.2.4 /Apache xserve very well >> and >> quite stable. >> >> What list seems to say: WebStar does not work (i did not try, but if >> there >> is somebody on the list, who works with witango/Webstar on OSX, let me >> know) >> >> Christian >> > > ________________________________________________________________________ > TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED] > with unsubscribe witango-talk in the message body ________________________________________________________________________ TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED] with unsubscribe witango-talk in the message body