I think the general thought is that you don’t want that accessible externally. If you run it in direct connect mode and then make sure that port isn’t accessible via your firewall you should be “safe”.
-Lon On Tue, Oct 25, 2016 at 3:21 PM, Theodore Petrosky <tedp...@yahoo.com> wrote: > I think you are saying that JavaMonitor should only be accessed by the > direct connect port. > > I never read that anywhere, and I have alway create an instance to > JavaMonitor. Is this a bad practice? > > Please be kind, I am showing my ignorance here hoping to be edified. > > > Ted > > > On Oct 25, 2016, at 6:17 PM, Paul Hoadley <pa...@logicsquad.net> wrote: > > Hi Ted, > > On 26 Oct 2016, at 2:48 AM, Theodore Petrosky <tedp...@yahoo.com> wrote: > > Why is it that I can only access the application scheduling or Application > Settings sections of JavaMonitor when I access it with the direct connect > (:56789)? these sections are not accessible if I use the running app. > http://something.com/apps/Webobjects/JavaMonitor > > > Are you doing something strange here? Why is JavaMonitor even accessible > via that URL? > > > -- > Paul Hoadley > http://logicsquad.net/ > > > > > > _______________________________________________ > Do not post admin requests to the list. They will be ignored. > Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) > Help/Unsubscribe/Update your Subscription: > https://lists.apple.com/mailman/options/webobjects- > dev/lon.varscsak%40gmail.com > > This email sent to lon.varsc...@gmail.com >
_______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
