From: Yariv S. <ya...@gm...> - 2006-06-20 03:56:39
|
Hi, I just made a clean install of Yaw 1.63 on my MacBook, and I'm experiencing some strage behavior. When I start Yaws, I see the following log lines: =INFO REPORT==== 19-Jun-2006::23:35:08 === Yaws: Listening to 0.0.0.0:8000 for servers - http://mb.local:8000 under /Users/yariv/Desktop/yaws-1.63/yaws/scripts/../www - http://localhost:8000 under /tmp mb.local is my computer's self assigned domain. When I go to http://mb.local:8000 in the browser, the browser hangs for a while. Apparently, the browser can't resolve the host name. Indeed, typing "host mb.local" yields mb:~ yariv$ host mb.local Host mb.local not found: 3(NXDOMAIN) However, when I manually type my IP address, http://192.168.1.110:8000/, I see the proper Yaws welcome page. This is a bit weird, but it looks like a Mac issue, and at least Yaws works. Now to the weirder issue: I created a file "test.yaws" in /tmp with the following content: <erl> out(A) -> {ehtml, {p, [], "foo"}}. </erl> For some reason, when I go to http://localhost:8000/test.yaws, Yaws returns to the browser the source code of test.yaws, not the result of the compiled page. This happens with any .yaws file -- Yaws never compiles it. This problem does not show up with the former access method: http://192.168.1.110:8000/. To summarize, 'localhost' works fine, but both 'mb.local' and '192.168.1.110' break in different ways. Has anyone noticed such behavior? If so, have you been able to fix it? Thanks in advance Yairv |