thanks, looks like the same error message is buried in that change / code, yes - though i am no closer to discerning the original cause of the error being triggered, since i am not familiar with the nginx sourecode at this point. any tips are welcomed!
Posted at Nginx Forum: http://forum.nginx.org/read.php?2,254523,254525#msg-254525 _______________________________________________ nginx mailing list [email protected] http://mailman.nginx.org/mailman/listinfo/nginx
