nitrogenproject.com in WebKit

28 views
Skip to first unread message

genthaler

unread,
May 3, 2010, 10:33:01 AM5/3/10
to Nitrogen Web Framework for Erlang
Is anyone else having problems seeing nitrogenproject.com via Safari
4.05 on MacOSX 10.6.3?
Safari seems to be seeing the index page as a downloadable artefact,
so I end up with a file called Untitled in my Downloads folder.
Seems to be a WebKit issue, same problem in Cruz, Fluid, OmniWeb,
Sunrise.
Camino & Firefox are OK.

--
You received this message because you are subscribed to the Google Groups "Nitrogen Web Framework for Erlang" group.
To post to this group, send email to nitro...@googlegroups.com.
To unsubscribe from this group, send email to nitrogenweb...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/nitrogenweb?hl=en.

Rusty Klophaus

unread,
May 5, 2010, 7:00:27 AM5/5/10
to nitro...@googlegroups.com
Hmm... that is odd... I just tested in Safari and Fluid, and both work fine.

Safari - Version 4.0.5 (5531.22.7)
Fluid - Version 0.9.6 (0.9.6)

What versions to do you have?

Best,
Rusty

Allan Streib

unread,
May 5, 2010, 9:31:15 AM5/5/10
to nitro...@googlegroups.com
Looks good for me in Safari 4.0.5 as well as Firefox 3.6.3.  I'm on Mac OS X 10.5.8 though.
 
Allan
 
On Wed, 05 May 2010 07:00 -0400, "Rusty Klophaus" <rklo...@gmail.com> wrote:
Hmm... that is odd... I just tested in Safari and Fluid, and both work fine.
 
Safari - Version 4.0.5 (5531.22.7)
Fluid - Version 0.9.6 (0.9.6)
 
What versions to do you have?
 
Best,
Rusty
 
 
 Mon, May 3, 2010 at 10:33 AM, genthaler <gent...@mac.com> wrote:
Is anyone else having problems seeing nitrogenproject.com via Safari
4.05 on MacOSX 10.6.3?
Safari seems to be seeing the index page as a downloadable artefact,
so I end up with a file called Untitled in my Downloads folder.
Seems to be a WebKit issue, same problem in Cruz, Fluid, OmniWeb,
Sunrise.
Camino & Firefox are OK.

Steve Davis

unread,
May 6, 2010, 4:53:07 AM5/6/10
to Nitrogen Web Framework for Erlang
Hi,

I suspect it's related to the fact that the server at
nitrogenproject.com is not setting the content-type header on its
responses, and that most but not all clients are "guessing" the
mimetypes correctly.

/s

Rusty Klophaus

unread,
May 12, 2010, 7:19:33 AM5/12/10
to nitro...@googlegroups.com
Thanks Steve, good catch, this is now filed as a bug: http://nitrogen.lighthouseapp.com/projects/21480-nitrogen/tickets/60
Reply all
Reply to author
Forward
0 new messages