• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Access to running WO app via network
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Access to running WO app via network


  • Subject: Re: Access to running WO app via network
  • From: David Teran <email@hidden>
  • Date: Fri, 18 Nov 2005 13:46:32 +0100

WOHost can be quite confusing. You should only use it if you have problems or really want that the apply only 'listens' on that address.

just my 2ct.

david


Am 18.11.2005 um 13:41 schrieb Hans-Martin Mensch:

You are absolutely right, thanks for the tip. But I had still another problem which I already solved, but want to share here:
Some time ago I added an application argument -DWOHost=localhost. I had to do this for Safari, cause it doesn't work with the default host name in the URL (funny enough OmniWeb does not have this problem). But now the "localhost" in the URL prevents a browser from another computer to access my application, since localhost is another address. So I had to change this again to the default setting using the host name to be able to access my app via network.


On 18.11.2005, at 10:18, David Teran wrote:

For testing purposes I need to access my running WO application (in development mode, started from Xcode) from another machine (Windows PC) inside our LAN. But I can't use the URL I have on my local browser (which is something like "http://localhost:54342/ cgi-bin/WebObjects/SkillPortal.woa"). Of course I replaced localhost with the IP address.

Is there a way to do it? The firewall on my Mac is on, but Personal Web Sharing is enabled as well.

... look at the url: you are using a custom port: 54342, this is not the port from HTTP which is (usually) 80. So even if personal web sharing is OK for your firewall the firewall will block access to port 54342 unless you open this port. I suggest using - WOPort=54342 for the application as additional argument and then open this port in the firewall. Using this WOPort tells the app to always use this port (unless you change the argument...).


david


_______________________________________________
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
  • Follow-Ups:
    • Re: Access to running WO app via network
      • From: Lachlan Deck <email@hidden>
References: 
 >Access to running WO app via network (From: email@hidden)
 >Re: Access to running WO app via network (From: David Teran <email@hidden>)

  • Prev by Date: Localized Date Formatting
  • Next by Date: Re: SharedEditingContext Write Locks?
  • Previous by thread: Re: Access to running WO app via network
  • Next by thread: Re: Access to running WO app via network
  • Index(es):
    • Date
    • Thread