Matt Sergeant writes: > On Tuesday 11 June 2002 8:49 pm, Ken Neighbors wrote: > > [AxKit] [Error] xmlParse returned error: 4, Start tag expected, '<' not > > That might be because to get the start tag I pass in the first 200 > bytes or so to the parser, but I do this as a string, and libxml2 > doesn't support gunzipping for a string. I guess you need to go the > provider route instead.
Ok. > You're talking about a generic problem with OO, and I don't think > anyone has ever solved it fully (there are Interfaces and Mixins as > alternate ways to "fix" this but they all have problems in the > scenario you describe), so we'll just have to suck it and see. I > still think despite this problem that an alternate provider is the > best way to solve your problem. I'll give it a try as an alternate provider. But to support it there still needs to be a patch to ConfigReader to reset the Content-Encoding when AxGzipOutput is Off. In a nutshell this is what happens: when "AddEncoding x-gzip .gz" is present in httpd.conf, then mod_mime sets the Content-Encoding to x-gzip whenever a compressed file is accessed. However, if AxKit handles delivery of the request and AxGzipOutput is Off, then the Content-Encoding needs to be reset. But if AxKit declines to handle the delivery, then it needs to leave the Content-Encoding as-is. I found that the best place to put this logic was in ConfigReader::DoGzip because that is where AxKit fiddles with the Content-Encoding header. I tried putting this logic in File.pm, but at that point AxKit does not yet know if it is going to handle the deliver or not (it declines when the xml file has no stylesheets). Ken --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
