You’ll be able to look at that header using the program “curl” on the command line. The finished module is going to put a header on every page that counts up the number of requests that process has served. This module will do nothing, which is only slightly less than what the finished module will do. To properly diagnose the problem, we need a backtrace to see what is happening behind the scenes. You should be able to go to in your browser and see the boilerplate text from Apache. 15:07 UTC Thank you for this bug report. On the Mac, start it by going to Sharing in your System Preferences and turning on Web Sharing. If you’re using Leopard, you’ll need to install the Developer Tools that came with your Mac so that you have the Gnu C Compiler. Leopard uses Apache 2.2, so that’s what I’m using. I’m doing this on OS X Leopard, so some of my notes will be specific to that. I’m going to try to give you everything you need to compile a very simple working module. It might be useful to others, and if I’m doing this completely wrong you can let me know! So I’m going to see about blogging the learning process for my module. Much of the documentation-even on the Apache web site-is 1.3 documentation retitled as 2.0. Most seem to either start well into the process instead of at square one, or provide non-working examples that don’t even go so far as to actually compile a working module. There doesn’t appear to be a whole lot in the way of really simple Apache module writing tutorials. One of the items on my task list for a long time now has been a specialized module for Apache.
0 Comments
Leave a Reply. |