ifying
an actual address in the Apache conf can work too, provided
it isn't actually an IPv6 address.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Douglas Burchard
Sent: Wednesday, March 17, 2004 07:37 PM
To: Webware Discuss
Subject: Re: [Webware-
`netstat` will tell you
`netstat -an` will give you all the ports sorted by ip6, ip, udp,
UNIX. (the -a will stop DNS lookups)
assuming this is what you meant...
* Douglas Burchard <[EMAIL PROTECTED]> [2004-03-17 22:39]:
> On Mar 16, 2004, at 4:50 PM, Nick Ragouzis wrote:
>
> > I've odds that y
On Mar 16, 2004, at 4:50 PM, Nick Ragouzis wrote:
I've odds that you'll find that John Dickinson's suggestion
was the ticket (viz: localhost -> 127.0.0.1 ... or whatever
specific address you want).
If you do confirm that we'd have confirmation of the
'bug' and 'fix' on Linux, Windows, and Mac OS.
est,
--Nick Ragouzis
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Douglas Burchard
Sent: Tuesday, March 16, 2004 04:24 PM
To: Webware Discuss
Subject: Re: [Webware-discuss] Getting Webware running on Mac OS X
On Mar 16, 2004, at 3:12 PM, Todd Grimason wr
On Mar 16, 2004, at 3:12 PM, Todd Grimason wrote:
Could it be you're requesting "/mk" when your Webware apache directive
is the more common "/wk"?
Okay, that *could* have been a typo in my email, but embarrassingly
(and as much as I wish it was) it wasn't. It didn't solve my problem,
but pointed
* Douglas Burchard <[EMAIL PROTECTED]> [2004-03-16 16:15]:
> The 404 page simply generates what I would expect:
>
> [Tue Mar 16 10:04:24 2004] [error] [client 127.0.0.1] File does not
> exist: /Library/WebServer/Documents/mk
Could it be you're requesting "/mk" when your Webware apache directive
Do you also have:
LoadModule webkit_module libexec/httpd/mod_webkit.so
AddModule mod_webkit.c
... in your httpd.conf file?
--T
On Mar 16, 2004, at 11:18 AM, Douglas Burchard wrote:
WKServer localhost 8086
SetHandler webkit-handler
---
On Mar 16, 2004, at 9:37 AM, Roger Espinosa wrote:
Mmm. This is a lark, but you didn't say --- you'll need to do
sudo apachectl graceful (or restart)
Nice catch, but just my bad typing. I did in fact use sudo when
restarting apache. :-}
You should also check what's showing up in /var/log/httpd
Is your /etc/hosts file set up improperly, by any chance?
On Tue, 2004-03-16 at 15:13, John Dickinson wrote:
> I had the same problem on my OS X box at home. My solution was to change
> the Location tag in the apache config to 127.0.0.1 (instead of localhost).
> It seems to work fine after I did
On Mar 16, 2004, at 9:59 AM, John Dickinson wrote:
I had the same problem on my OS X box at home. My solution was to
change the Location tag in the apache config to 127.0.0.1 (instead of
localhost). It seems to work fine after I did that.
Hmm, I changed 'WKServer localhost 8086' to 'WKServer 127
I had the same problem on my OS X box at home. My solution was to change
the Location tag in the apache config to 127.0.0.1 (instead of localhost).
It seems to work fine after I did that.
--John
At 11:18 AM 3/16/2004, Douglas Burchard wrote:
First post, have only been lurking about 12 days...
On Tue, Mar 16, 2004 at 09:18:29AM -0800, Douglas Burchard wrote:
> First post, have only been lurking about 12 days...
>
> I've been stymied trying to get Webware/WebKit/mod_webkit to work on a
> Mac OS X 10.3.2 machine. Everything seems to load okay, so either I'm
> missing something really ob
First post, have only been lurking about 12 days...
I've been stymied trying to get Webware/WebKit/mod_webkit to work on a
Mac OS X 10.3.2 machine. Everything seems to load okay, so either I'm
missing something really obvious, or something is interfering with the
works. Here's what I've done:
13 matches
Mail list logo
