Hi Robert, Although my analysis is not very thorough or scientific, I can tell you assigning the httpHeader System variable in Witango gives some control of the HTTP Header information - but not all of it.
Your code example actually shows the same conclusion for both Mac and Windows. In your assignment, you've got: HTTP/1.1 200 OK<@crlf>Server: WiTango v4.05.047<@crlf>MIME-Version: 1.0<@crlf>Content-Type: image/jpeg<@crlf><@crlf> Where you're setting 'Server: WiTango v4.05.047' - but both your Mac and Windows results show the 'Server' property having different values, demonstrating whatever bug you've found is the same on either platform. Also your 'HTTP/1.1' appears as HTTP/1.0 on your Mac output. In my experience, on Windows, I am able to control things like Content-Type and Content-Length, Cache settings and Cookies - the rest have not proved to be overlly important (so far). The fact that some Web-servers will assign extra information, such as Server (type) and Creatation date does not typically hinder your application. Most web-servers, such as IIS, allow you to define your default Header data outside of your application as well. If you want to set your Server type, I think the closest you'll get using the 'X-' prefix. Although I can't quote the standard (because I can't remember where I read it) you can insert custom information in your headers if you prefix it with X-. Example: <@assign local$httpHeader value="X-Powered-By: Witango XML-RPC 0.9 X-Author: Scott Cadillac [EMAIL PROTECTED] Cache-Control: no-cache, max-age=0, must-revalidate, proxy-revalidate Pragma: no-cache Content-Type: image/jpeg "> And Yes, I agree, it would be nice to have a clear definition as to which properties of the Header we have control of and which we don't - although I'm sure mileage will vary depending on the Web-server brand. This is a very interesting topic and thank you for bringing it up Robert. As a suggestion, it would be great to have an extended set of Server Variables for things like the httpHeader_ContentType or even httpHeader_StatusCode, it make this more efficient. At one point I started to bring this up at the Conference, but we all got distracted onto something else. I'll try and write this up formally and submit it to With. Cheers.... Scott Cadillac http://xml-extra.net [EMAIL PROTECTED] ----- Original Message ----- From: "Robert Garcia" <[EMAIL PROTECTED]> To: "Multiple recipients of list witango-talk" <[EMAIL PROTECTED]> Sent: Saturday, May 04, 2002 1:43 AM Subject: Witango-Talk: Tango HTTP Header Bug? Ever since I have switched my apps from Mac OS 9/WebStar/Tango 4.05.047 to Win2000/IBM HTTP/Tango 4.05.047 I have noticed some bizarre results with some of my apps, especially when I modify the HTTP Header. After doing some research/Testing, I have found the following: Here is what I am assigning the HTTP Header to be: HTTP/1.1 200 OK<@crlf>Server: WiTango v4.05.047<@crlf>MIME-Version: 1.0<@crlf>Content-Type: image/jpeg<@crlf><@crlf> Short and simple, works. Now I take the same taf that serves a JPEG and run it on the mac, and the other on the windows setup. Then I test the contents of the header. For those of you who don�t know to do this, you use telnet to telnet into your web server and pretend your a browser. From my OS X Terminal I type: telnet www.mysite.com 80 This connects me and gives me a response like this: Connected to www.mysite.com. Escape character is '^]'. I then manually type in a request like I am a browser (I am using the minimal info necessary): GET /thumb.taf?key=13 HTTP/1.1 [HIT RETURN] Host: www.mysite.com [HIT RETURN 2X] You must add the host line on a virtual host web server, so that it knows where to find the file. Now the results from the Mac/Tango system: HTTP/1.0 200 OK Server: WebStar/1.0 ID/ACGI MIME-Version: 1.0 Content-Type: image/jpeg [the binary info follows the header] As you can see, the Mac system is using the header I told it too. Now here are the results from an identical taf file on the Win2000/Tango server: HTTP/1.1 200 OK Date: Sat, 04 May 2002 08:24:30 GMT Server: IBM_HTTP_SERVER/1.3.19.1 Apache/1.3.20 MIME-Version: 1.0 Transfer-Encoding: chunked Content-Type: image/jpeg [the binary info follows the header] It correctly set the contentType, but it is not my header. So my question to the list is this: Could this just be my use of the IBM HTTP Server? Does the happen on IIS or Netscape servers? What about linux? Serving binary data is a very important part of app serving with Tango. Any info we can pass to Phil and the team would really be great, I know they are working on this. Plus, I want fix this. -- Robert Garcia BigHead Technology 21053 Devonshire Suite 206 Chatsworth, Ca 91311 Phone 818.773.8162 Fax 818.773.8164 http://www.bighead.net/ [EMAIL PROTECTED] ________________________________________________________________________ TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED] with unsubscribe witango-talk in the message body
