I always do dev in direct connect with ssl enabled :) Apache annoys me when it 
times out a page while I’m at a breakpoint. People also have a nasty habit of 
using Apache’s doc root as an excuse to fail to use /WebServerResources/ 
properly. JS and CSS outside of version control is a major pet peeve of mine.

#########################################################################
# SSL DirectConnect
#########################################################################
## You should probably not enable any of these settings in a normal Apache 
webserver deployment,
## in particular the ssl port property, as this is used by ERX to generate 
https URLs, which must
## match your Apache config.
##
## To enable SSL support with DirectConnect, you must do the following:
##
## * In your Resources folder, run "keytool -genkey -alias WebObjects -keyalg 
RSA -keystore adaptorssl.key".  Select a 
##   password for your keystore (i.e. "changeit"), and set the "your first name 
and last name" field to match the hostname 
##   that you will be running your directconnect app off of.
## * In your Resources folder, create an executable script (it MUST BE 
EXECUTABLE) named "adaptorsslpassphrase" with the
##   contents:
##   echo changeit
##   where you should replace "changeit" for whatever password you selected in 
the previous step.
## * Set the following property to true
#er.extensions.ERXApplication.ssl.enabled=true

## (optional) To specify an SSL host name other than what is returned from a 
call to
## application.host(), you can override it below  
#er.extensions.ERXApplication.ssl.host=localhost

## (optional) To select an SSL port other than 443, uncomment the following. If 
you are already running Apache with SSL,
## you probably want to set this.  If the port number is 0, the SSL port will 
be automatically assigned (using the same
## mechanism that WO uses to set the regular port) 
#er.extensions.ERXApplication.ssl.port=0

# Enable SSL for direct connect so running Apache locally is unnecessary
er.extensions.ERXApplication.ssl.enabled=true
er.extensions.ERXApplication.ssl.host=localhost
er.extensions.ERXApplication.ssl.port=4443

On Aug 5, 2014, at 9:08 AM, Mark Wardle <[email protected]> wrote:

> Yosemite upgrades Apache from 2.2 and 2.4.
> 
> I’ve tried recompiling the apache adaptor but compilation files despite 
> entering a magic incantation:
> 
> make ADAPTORS=Apache2.4 LTFLAGS='--tag CC’
> 
> 
> /usr/share/apr-1/build-1/libtool: line 8962: 
> /Applications/Xcode.app/Contents/Developer/Toolchains/OSX10.10.xctoolchain/usr/bin/cc:
>  No such file or directory
> apxs:Error: Command failed with rc=8323072
> 
> It looks like it may be a problem with the new yosemite Xcode but I’m not 
> sure.
> 
> Has anyone either downgraded gracefully to apache 2.2 or got a binary apache 
> 2.4 mac os x yosemite adapter. For the latter, we then have to do battle with 
> the updated configuration files which look like they’re more restrictive than 
> before.
> 
> If this doesn’t work, then I might have to face the horror of remembering how 
> to do development in direct connect mode and somehow dynamically switch SSL 
> on or off depending on whether in development!
> 
> Mark
> -- 
> Dr. Mark Wardle
> Consultant Neurologist, University Hospital Wales, Cardiff, UK
> Email: [email protected] or [email protected]  Twitter: @mwardle
> Telephone: 02920745274 (secretary) or facsimile: 02920744166
> 
> 
> 
> 
> 
> _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Webobjects-dev mailing list      ([email protected])
> Help/Unsubscribe/Update your Subscription:
> https://lists.apple.com/mailman/options/webobjects-dev/rgurley%40smarthealth.com
> 
> This email sent to [email protected]


 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      ([email protected])
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com

This email sent to [email protected]

Reply via email to