The apachectl files reads/sources the /etc/rc.conf file. Because rc.conf reads in rc.conf.local, your commands to load ddclient are executed. So you have to take these commands out and put them in the proper file /etc/rc.local

Does the Apache logs complain that it cannot find your css file?

__________________
You don't need to be a genius to debug a pf.conf firewall ruleset, you just need the guts to run tcpdump

The apachectl files reads/sources the /etc/rc.conf file. Because rc.conf reads in rc.conf.local, your commands to load ddclient are executed. So you have to take these commands out and put them in the proper file /etc/rc.local

Thanks! I was asleep at the wheel

Quote:

Does the Apache logs complain that it cannot find your css file?

The logs don't contain any errors relating to the css file, that I can find.

Having tried getting Apache going on my OpenBSD 4.3 box (I'm not used to 1.3.x), I noticed this peculiarity as well. Forgive posting in an old thread but I've found some thing interesting:

I wanted to test to ensure every thing works in my apache setup before configuring virtual hosts for several projects, so I copied a small template for a home page I made awhile back but noted that my CSS file was not being loaded when testing it.

I found some thing rather odd though, the access log was showing a successful hit on the stylesheet but it would only work in Mozilla if I made it an internal style sheet (no @import or <link>) in my index.html.

After racking my head a bit and exhaustingly reviewing every configuration option I know of without finding any problems in my setup. Then I had a brain fart, every test I had made was via Firefox or Flock over the LAN or Lynx on the server. So I've fired up another machine and ran through tests on the following browsers:

I found some thing rather odd though, the access log was showing a successful hit on the stylesheet but it would only work in Mozilla if I made it an internal style sheet (no @import or <link>) in my index.html.

So I've fired up another machine and ran through tests on the following browsers:

Yes, it works with IE6...what's also odd is that CSS validation returns "I/O error: unknown file type: text/plain" -- but the file is saved as .css -- I wonder if it's a byte-order mark issue or if the .css file has non-Unix line endings?

Let me put it this way, Firefox (and apache) is (are) to fat to look threw the code to find out lol.

I think HTTP request messages are supposed to be termnated with a carriage return and line feed. But I've never bothered to read the standard, so I'm not sure what clients receive (\r\n or actual file content byte by byte).

I've tested with my stylesheet using both \n and \r\n formats with the same results.