• 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: https and Deployment: Reality deviates from Documentation?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: https and Deployment: Reality deviates from Documentation?


  • Subject: Re: https and Deployment: Reality deviates from Documentation?
  • From: Chuck Hill <email@hidden>
  • Date: Mon, 2 Apr 2007 10:08:00 -0700


On Apr 2, 2007, at 6:50 AM, Greg Brown wrote:

I am running ( trying) Myapp.woa with apache 1.3, Mac OSX 10.4.8 and the documentation doesn't appear to be right! or I misunderstand, so for the record:

Documents say:
However, most web applications contain web server resources, such as images. You should place these resources in the web server’s Document Root directory. You accomplish that by performing a split installation.
If I use https to access Myapp.woa, then it seems a split install is necessary. Is that manditory? a split install? if so maybe it should say: "You MUST

What are you seeing that makes you think that?


place these resources in the web server’s Document Root directory.....

A second misunderstanding/documentaion question:

It says (on the Application tab) that when configuring an application one could use any name they wanted for the application's name in the Monitor program, e.g., for Myapp.woa I could call it application Test, then give the path to Myapp.woa/ Myapp. Well of course that doesn't appear to work with https! With https the Test app will look for resources in Test.woa, which does not exist. The only way I could get this to work was ignore the documentation and have the Monitor application name match exactly the Myapp.woa name.

Are these realities localized to just my machine? or should the documentation be changed?

You have done / are doing something wrong or not doing something that needs to be done. Or something... :-) We use https and names in monitor that differ from the app name file system all the time with no problems at all. What exactly are you doing / trying to do and what are you seeing? Are you perhaps running in Direct Connect mode (URL like http://some.domain.com:3456/...). Direct Connect (besides being evil and a toy) does not support HTTPS.


Chuck

--

Practical WebObjects - for developers who want to increase their overall knowledge of WebObjects or who are trying to solve specific problems.
http://www.global-village.net/products/practical_webobjects






_______________________________________________
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: https and Deployment: Reality deviates from Documentation?
      • From: Greg Brown <email@hidden>
References: 
 >https and Deployment: Reality deviates from Documentation? (From: Greg Brown <email@hidden>)

  • Prev by Date: Re: Writing IE specific code
  • Next by Date: Re: Writing IE specific code
  • Previous by thread: https and Deployment: Reality deviates from Documentation?
  • Next by thread: Re: https and Deployment: Reality deviates from Documentation?
  • Index(es):
    • Date
    • Thread