µTasker Forum
µTasker Forum => µTasker general => Topic started by: Thomas on January 29, 2008, 12:20:13 PM
-
Hi Mark,
Just want to suggest a future feature, HTTP Response Headers.
I think it could be nice in many situations to easily add HTTP Response Headers to files being transmitted from the web-server. For instance to instruct the client about cache control as some clients will cache pages depdending on settings and display outdated files. Or for instance to raise the "save file as" dialog for given files instead of displaying the file inside the browser or depend on the browser to interpret files correctly. Maybe implemented as a global default header with possibility for overriding for given files or criterias.
I've implemented what I need for my project in this regard though, but might be useful I think for more people in a general way.(?)
-
I second the proposition.
The problem with having no HTTP headers is that you rely on the browser default behaviors, especially when handling file types and caching. For example when no headers are provided Firefox will generally not cache anything, which makes browsing slow because common items (gif, css, xsl) are fetched every time. IE does the opposite by caching too much: async requests made through XmlHttpRequest() are cached by default which might create problems when trying to display real-time informations. Also, when the browser does not have a Content-Type header it will try to detect content-type by file extension. This might lead to inconsistent behavior between browsers. Also, some applications or libraries might not play nice with headerless HTTP responses. I know that the HTTPClient object from the .NET Framework will throw an exception when no headers are provided.
-
Hi All
Thomas - You seem to have done some work along these lines. Can you (or someone else with experience) give a short example with technical details (at lowish level) so that I am sure that I know the best way to realise this correctly?
Thanks
Regards
Mark
-
Hello Mark,
The HTTP Header issue is currently listed as a future enhancement in our development tracking system.
I can provide the source code when it's completed, however I don't know when.
-
Hi Phil
That's interesting news.
If you find any difficulties with the integration just send me an Ethereal/Wireshark recording so that I can help out.
Good luck
Regards
Mark
-
Mark,
The HTTP Response Header feature did evolved?
Regards,
Marcelo Costa
-
Hi Marcelo
Yes, this is available in some of the latest service packs (which package are you using?). It is activated by setting the define SUPPORT_CHROME in config.h.
The reason that it has this name is because CHROME refuses to accept any web pages without this header (and has a couple of other strange habits too... - see http://www.utasker.com/forum/index.php?topic=446.0).
If you don't find this in your package just let me know and I'll send the HTTP.c file and a new tcpip.h - this should enable it to run on any package then.
Regards
Mark
-
Hi Mark,
Glad to hear from you.
I am use the SP8 but I can´t find the CHROME directive.
btw, did you have time to dig into the snmp code that I send to you?
Regards,
Marcelo Costa
-
Hi Marcelo
I have sent you new files so that you can use the HTTP header support if you need it.
I haven't worked on SNMP for some time so didn't study your modifications yet. Recently the M5225X support had priority due to the chips' release recently, and also USB device support for all packages (quite a lot of work....!).
Then high priorities are USB host and OTG, with mass storage support. On the Ethernet side cURL, FTP client, IPV6 are on the list and SNMPV1,V2 and V3 should sometime really be fully supported. This means that I won't be looking at SNMP in the every near future but will certainly get back to it as soon as possible.
Hopefully your work is going well!!
Regards
Mark
-
Hi Mark,
Thank you for the files.
I cut the SUPPORT_CHROME parts and past in the old http.c.
My project uses ajax and XML to update data in a web page. Every thing works fines in Mozilla and CHROME now, except for IE.
IE insist to cache the XML file that is a txt with some £vXY commands.
I am modifying the http.c file to include the xml header response.
After that I will return to the SNMP development.
If you need help in any development or test, please call me.
-
Hi Marcelo
Can you add a meta tag somewhere to inform IE not to cache things?
I don't work with AJAX and XML (although I probably should be doing so...) so am interested in your results.
Good luck
Regards
Mark
-
Hi Mark,
I added the meta tags in the html source, but the problem is that IE cache the XML file. Don´t ask why ;)
After I modified the http.c source file to support differents header responses based on mime type, I got
a strange content for the xml file. Extras bytes are added at the end of the response of the web server.
Other mime types are OK because the are responded with the http header.
I will send you the http.c and wireshark file, I would like if you could open them.
The xml and ajax are fully functional at chrome and mozilla, the problem is the IE that caches the xml.
I can send you the javascript function and an html sample using it.
I readed somewhere that is possible to create a file on the fly, but I thing that it would make the application more complicated.
Regards,
Marcelo Costa
-
Hi Mark,
I finally made the IE work. Follows the headers that I modified:
#ifdef SUPPORT_CHROME // {34} Chrome requires that the web server always sends a HTTP header otherwise it refuses to operate
static const CHAR cucHTTP_header[] = "HTTP/1.1 200 OK\r\nConnection: close\r\nCache-Control: no-cache \r\n\r\n";
#define SIMPLE_HTTP_HEADER_LENGTH (sizeof(cucHTTP_header) - 1)
#ifdef SUPPORT_MIME_IDENTIFIER
static const CHAR cucXML_header[] = "HTTP/1.1 200 OK\r\nConnection: close\r\nContent-Type: text/xml\r\nCache-Control: no-cache \r\n\r\n";
#define SIMPLE_XML_HEADER_LENGTH (sizeof(cucXML_header) - 1)
#endif
#endif
Regards,
Marcelo Costa
-
Sorry to dig up this old post, but I was having the same issues. Chrome and FF worked OK, but IE kept dying on me. Turns out that IE absolutely REQUIRES that the Content-Type be set for XML, and there is no way to fix this on the client side. Chrome and FF look for the MIME type, but fall back to the file extension, IE just dies without it.
Anyways, I followed mcosta's suggestion, but also had to add a section where the content type was to be written to the client.
I created a new MIME type in config.h, and added the following lines to http.c:
(line number approx 379)
#ifdef SUPPORT_CHROME // {34}
if (http_session->ucMimeType == MIME_XML) //PCK 12/21/2009 -- added XML type
uMemcpy(HTTP_Tx->ucTCP_Message, cucXML_header, SIMPLE_XML_HEADER_LENGTH); // copy the XML header
else
uMemcpy(HTTP_Tx->ucTCP_Message, cucHTTP_header, SIMPLE_HTTP_HEADER_LENGTH); // copy the HTTP header to start of each file to be transferred
fnGetParsFile(http_session->ptrFileStart, (HTTP_Tx->ucTCP_Message + SIMPLE_HTTP_HEADER_LENGTH), (usLen - SIMPLE_HTTP_HEADER_LENGTH)); // get a frame to send
http_session->ptrFileStart -= SIMPLE_HTTP_HEADER_LENGTH; // offset for the added header
#else
and
(line number approx 911)
#ifdef SUPPORT_CHROME // {34}
if (http_session->FilePoint == 0) // regeneration of first frame needs to be handled differently to insert the HTTP header
{
if (http_session->ucMimeType == MIME_XML) //PCK 12/21/2009 -- added XML type
uMemcpy(HTTP_Tx->ucTCP_Message, cucXML_header, SIMPLE_XML_HEADER_LENGTH); // copy the XML header
else
uMemcpy(HTTP_Tx->ucTCP_Message, cucHTTP_header, SIMPLE_HTTP_HEADER_LENGTH); // copy the HTTP header to start of each file to be transferred
fnGetParsFile((http_session->ptrFileStart + SIMPLE_HTTP_HEADER_LENGTH), (HTTP_Tx->ucTCP_Message + SIMPLE_HTTP_HEADER_LENGTH), (Len - SIMPLE_HTTP_HEADER_LENGTH)); // get a frame to send
}
else {
fnGetParsFile((http_session->ptrFileStart + http_session->FilePoint), HTTP_Tx->ucTCP_Message, Len);
}
#else
Just do a search on the two places the cucHTTP_header is used, and add/replace the code with the above.
Mark, perhaps it would be better to create a "generic" Content-Type handler???
-
Hi Paul
It may be that you don't have this in your version yet but the development version has a routine called fnGenerateHTTP_header() which is used to generate the header. Then uses a table of MIME types to define the header that is sent (in fact a table is a bit exaggerated since it only does TXT and HTTP, but could be extended to include any other types of interest). I have sent you the HTTP.c file as reference - not to use directly since it has other stuff which may not match exactly. I will add XML (as option) to the list as in your example.
Regards
Mark