76933 2012-01-24 12:59:04 -0800 NRWT fails to launch/kill Apache for Apple's Windows port 2013-05-29 14:40:55 -0700 1 1 1 Unclassified WebKit Tools / Tests 528+ (Nightly build) PC Windows 7 RESOLVED WONTFIX InRadar, NRWT, PlatformOnly P2 Normal --- 38756 1 aroben bfulgham bfulgham dpranke eric webkit-bug-importer oldest_to_newest 541582 0 aroben 2012-01-24 12:59:04 -0800 NRWT doesn't seem to be able to launch or kill Apache for Apple's Windows port. I believe there are at least two problems: 1) We use Apache 1.x, which doesn't support the "-k start"/"-k stop" options to apachectl 2) Our copy of Apache doesn't support SSL 541583 1 webkit-bug-importer 2012-01-24 12:59:26 -0800 <rdar://problem/10747576> 671818 2 dpranke 2012-07-17 17:56:16 -0700 looking at this now, and (as noted in an email) ... I don't actually know where to get a copy of apache for this cygwin config , so this'll be hard to fix :). 892927 3 bfulgham 2013-05-23 09:55:42 -0700 There seems to be a number of problems with Cygwin and Apache. Cygwin no longer ships Apache 1, and I cannot get the current build of Apache 2.2 that they distribute to run under Windows 7 or Windows 8. The lighttpd program seems to work properly, and starts up and shuts down cleanly under Cygwin. This seems like a better options, especially since this is how Blink is doing things. I briefly attempted to use the stock Apache Foundation's Windows build, but this was even more trouble: The PID generated by the program was a Windows PID (not a Cygwin PID), so the Cygwin kill logic did not properly stop the program. Even after writing conversion logic to get the Cygwin PID from the Windows PID, I found that Apache forks on Windows (creating at least two processes), only one of which is visible to Cygwin. Disaster! I am switching the Apple Windows port to lighttpd. 895224 4 bfulgham 2013-05-29 14:40:55 -0700 Apache on Cygwin does not seem usable at present. Closing this bug and switching over to lighttpd.