On Friday, December 6, 2002, at 10:40 AM, Puneet Kishor wrote:
is this something that could be traced to my web server configuration (both are running Apache, vanilla, ie, no mod_perl, etc.), or is it specific to cgi on macs?Yes, outputting forms is not supported on the Mac platform.
Doesn't that sound silly? :-)
But seriously now... Without seeing the code in question, it's impossible to say for certain what the problem is, but here are some things it might be useful to look at:
If you're using CGI.pm to generate the form elements, compare the module versions in use on the two servers. If they're different, compare the documentation on the methods/functions you're using - perhaps they've changed.
Check Apache's error log for any suspicious entries - really, any entries at all are suspicious. You're using strict and fatalsToBrowser, which *are* Very Good Things - but they're not substitutes for checking the error logs, as there could still be non-fatal warnings lurking there.
Save the output and validate it - the fact that it works in the Windows browsers you've checked it with does not prove that the HTML is free of errors, it simply indicates that any errors that may be in it are not fatal to those particular browsers. Browsers are, by design, remarkably tolerant of HTML glitches, but each has its own foibles - they are not, by any stretch of the imagination, a reliable means of error-checking.
If all else fails, try to reduce the code to a small piece of code that illustrates it, and post that code here. Unless there are known bugs in the CGI.pm module included with OS X that I'm unaware of, it's hard to give more than general guidelines without seeing your code.
sherm--
If you listen to a UNIX shell, can you hear the C?
