I was using the development tools in Safari. I suspect it would've
reported an error, had I actually looked at the error console. Instead I
was looking everywhere but there. Sometimes when you miss the obvious, it
becomes increasingly more difficult to find it again.
tom
On Tue, Jun 3, 2
> I didn't find the problem until I resorted to studying tcpdumps of the browser
> traffic to see the css file being transmitted over the wire.
FYI the developer tools in Chrome (or equivalents in firefox etc.)
also help tracking these kinds of issues, probably a little faster
then analyzing tcpdu
SOLVED.
My Apache installation was being crippled by an incomplete mime.types that
had no entry for css files. They were being served as text/plain, and
hence were being ignored by the browsers.
This is the most time I have ever wasted on a trivially stupid bug. I
didn't find the problem until
On 06/02/2014 11:42 PM, Fine, Thomas wrote:
> The insane part here is that (as far as I can tell) this dynamically
> generated file never ever ever actually needs to change unless I
> reconfigure or re-install puppet-dashboard. So alternatively if you can
> tell me how to just serve this as a plai
Hi,
My problem is that the CSS formatting in puppet dashboard does not show up
under apache, but works fine under webrick. This SOUNDS exactly like some
old bugs (9676, 9767), but I've applied all the recommended fixes to no
avail, and at an rate the symptoms are only the same on the surface.
My
