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 I resorted to studying tcpdumps of the
browser traffic to see the css file being transmitted over the wire.
tom
On Tue, Jun 3, 2014 at 5:57 AM, Felix Frank <[email protected]
> wrote:
> 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 plain file not generated by
> > passenger, that'd make me totally happy right now.
>
> Did someone say "silly workaround"? :)
>
> How about a caching (nginx) proxy in front of Apache that serves the CSS
> for you, while passing all other requests through to Apache?
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/puppet-users/538D9C0D.7030206%40alumni.tu-berlin.de
> .
> For more options, visit https://groups.google.com/d/optout.
>
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/CANVEBdjXa7zo%2BEHvSZD_pnu%3D6on843LNf9dX1ARRx4EkX0kN%2BA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
