NRWT fails to launch/kill Apache for Apple's Windows port

• Component: Tools / Tests
• Status: RESOLVED WONTFIX

[Adam Roben (:aroben)]

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

[Radar WebKit Bug Importer]

<rdar://problem/10747576>

[Dirk Pranke]

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 :).

[Brent Fulgham]

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.

[Brent Fulgham]

Apache on Cygwin does not seem usable at present.  Closing this bug and switching over to lighttpd.