Apache Mime Types

[kuiqsilver]

Howdy all, I'm running Apache 1.3 w/ MySQL 5 and PHP 5 on Slackware Linux 10.0.

I'm trying to implement CSS pop-out menus on my website, and I guess you can imagine what a terrific mess IE makes of that.

Anyhow, I'm trying to use an .htc file to 'fix' IE but I don't believe the file is reaching the client. I added the following line:

<i>text/x-component .htc</i>

to my mime.types file, but following an Apache restart it hasn't accomplished anything.

Ideas?

 

[feherke]

Hi

I don't believe the file is reaching the client
[gray](...)[/gray]
it hasn't accomplished anything

Could you explain why do you think so ?

Without involving a server, from the local harddisk works ?

That should work even without seting a proper MIME type.

Look at HTTP headers to see if the file arrives to the browser and if yes, what [tt]Content-type[/tt] header has. For this you can use FireFox with LiveHTTPHeaders extension. ( Or Explorer with ieHTTPHeaders. )

Feherke.

http://rootshell.be/~feherke/

 

[kuiqsilver]

Thanks, Feherke.

The HTTPHeaders extensions were a big help. The .htc file wasn't reaching the client though that turned out to be a syntax error in my CSS.

Having fixed that, it wasn't being sent as type text/x-component. I killed Apache, removed all temporary files, double checked my mime.types file, and restarted Apache. Thanks to the headers extension, I now know everything should be going swimmingly. However, the pop-outs don't pop out.

The relevant link is

http://neonbrainiac.nu/menu.php.

Anyhow, since my problem no longer seems to be with Apache, I need to begin hunting elsewhere.

Thanks again.

 

[NullTerminator]

So are you saying that the popouts work in FireFox?

if your request the css file directly in the url, does teh url resolve properly to the css file. Often the path to the css file is broken when things like this don't work.

Check the webserver logs. Do you see thge request for the css file. Is the status code 200 OK or 404 not found?

Jeb

 

[kuiqsilver]

Jeb;

Yeah, I checked the server logs and used Feherke's http headers utility. I had to dicker with the path a little bit for the .htc file and it finally was reaching the client (code 200) but it still had no effect in my Internet Explorer browsers. Firefox, Konqueror and Mozilla all worked fine; there was no problem with the path to the CSS. I gave up on the whatever:hover technique and used Suckerfish instead. It works like a charm now. At least in IE 5.0 and 6.0.