Re: Problems with Safari
Re: Problems with Safari
- Subject: Re: Problems with Safari
- From: Hans-Martin Mensch <email@hidden>
- Date: Sat, 23 Jul 2005 12:29:36 +0200
I found out that Safari has problems resolving the local network name
(http://MacDev.local:54919/...) which WO uses. If I replace the
machine name with its current IP address it works as fast as in other
browsers. Of course this is not a good solution.
Can I tell WO to use the IP address instead of the machine name?
How come that only Safari has a problem with it. All other browsers
work fine. Also a ping to the machine name works perfectly!
On 23.07.2005, at 11:35, Helge Städtler wrote:
Look out for missing images which are not found by the
WOResourceManager
this is often the cause for not completely loaded pages (which are
in return
not shown until loaded completely). had this behaviour wich favicon
and
blank.gif's once.
look in the run-log for more info. sometimes its also the /etc/hosts
configuration which cannot resolve the domainname which webobjects
chooses
for the machine.
at least on xServes its often a good idea to put the IP-address and
the
corresponding domainname manually in the /etc/hosts because for
some reasons
xServe setup leaves this to the user, and on mac os x machines this is
nearly never done for you.
Has someone a clou how I can get xCode 2.1 run in rapid turnaround
mode and
using correct URL's for startup? I think i have a problem wich mac
os x
naming the domainname in a "Bonjour"-like style
"blablasomething.local",
which cannnot be resolved by the wo-adaptor/apache nor the xCode...
regards,
helge
Am 23.07.2005 11:23 Uhr schrieb "Hans-Martin Mensch" unter
<email@hidden> / On 23.07.2005 11:23 Uhr "Hans-
Martin Mensch"
wrote using address <email@hidden>:
Hi,
I have a problem using Safari for WO Development (running the app
locally from Xcode). Safari needs a very long time (up to 1 minute)
for the response of the page. With other browsers (OmniWeb, Firefox)
this is not happening and the response is very quick. Safari works
fine with a WO app running on the server (normal connection). I'm not
sure, but I think this problem started after upgrading to Tiger.
Any ideas?
Hans-Martin
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
email@hidden
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden