Progress Report (Viewsource)

From my last post many of you might remember that the web application of viewsource was only displaying the python script code rather than executing it, this issue has been resolved.

CHANGES

httpd.conf

--------------------------------------------------------------------------------------
--- httpd1.conf 2010-01-25 23:07:00.000000000 -0500
+++ httpd.conf 2010-01-21 19:06:51.000000000 -0500
@@ -193,6 +193,8 @@
LoadModule cache_module modules/mod_cache.so
LoadModule suexec_module modules/mod_suexec.so
LoadModule disk_cache_module modules/mod_disk_cache.so
+#LoadModule file_cache_module modules/mod_file_cache.so (Had to comment out, errors)
+#LoadModule mem_cache_module modules/mod_mem_cache.so (errors, commented out)
LoadModule cgi_module modules/mod_cgi.so

#
@@ -314,7 +316,7 @@
# http://httpd.apache.org/docs/2.2/mod/core.html#options
# for more information.
#
- Options Indexes FollowSymLinks
+ Options Indexes FollowSymLinks ExecCGI

#
# AllowOverride controls what directives may be placed in .htaccess files.
@@ -558,7 +560,7 @@
# The same rules about trailing "/" apply to ScriptAlias directives as to
# Alias.
#
-ScriptAlias /cgi-bin/ "/var/www/cgi-bin/"
+#ScriptAlias /cgi-bin/ "/var/www/cgi-bin/"

#
# "/var/www/cgi-bin" should be changed to whatever your ScriptAliased
@@ -755,8 +757,8 @@
# Despite the name similarity, the following Add* directives have nothing
# to do with the FancyIndexing customization directives above.
#
-#AddEncoding x-compress .Z
-#AddEncoding x-gzip .gz .tgz
+AddEncoding x-compress .Z
+AddEncoding x-gzip .gz .tgz

# If the AddEncoding directives above are commented-out, then you
# probably should define those extensions to indicate media types:
@@ -778,7 +780,7 @@
# To use CGI scripts outside of ScriptAliased directories:
# (You will also need to add "ExecCGI" to the "Options" directive.)
#
-#AddHandler cgi-script .cgi
+AddHandler cgi-script .cgi (probably the issue, however viewsource.conf should have handled this and it wasn't)

#
# For files that include their own HTTP headers:
@@ -992,3 +994,24 @@
# ErrorLog logs/dummy-host.example.com-error_log
# CustomLog logs/dummy-host.example.com-access_log common
#
+
+# David Humphrey - enable gzip compression
+
+ AddOutputFilterByType DEFLATE text/plain
+ AddOutputFilterByType DEFLATE text/html
+ AddOutputFilterByType DEFLATE text/xml
+ AddOutputFilterByType DEFLATE text/css
+ AddOutputFilterByType DEFLATE application/xml
+ AddOutputFilterByType DEFLATE application/xhtml+xml
+ AddOutputFilterByType DEFLATE application/rss+xml
+ AddOutputFilterByType DEFLATE application/javascript
+ AddOutputFilterByType DEFLATE application/x-javascript
+
+ DeflateCompressionLevel 9
+
+ DeflateFilterNote Input instream
+ DeflateFilterNote Output outstream
+ DeflateFilterNote Ratio ratio
+
+ LogFormat '"%r" %{outstream}n/%{instream}n (%{ratio}n%%)' deflate
+
--------------------------------------------------------------------------------

If anyone knows if I can simply add this stuff to viewsource.conf so that I don't have to deal with making a patch for httpd.conf and deal with permission it would be greatly appreciated.

CHANGES 2

Viewsource.conf

Addhandler cgi-script .cgi .py .pyc .pyo (bold added)

ISSUES LEFT

Web application only displays errors when "setenforce 0" if "setenforce 1" then a pop up comes up saying error but does not describe the error. I need to figure out how to fix the permissions within my spec file so that it will work while in "setenforce 1" mode. Any suggestions would be greatly appreciated.

Stay tuned for the soon to come release...

Release Plan

As some of you might remember I was working on packaging viewsource last semester and ran into some issues with the web application only pulling up the python script when the buttons were pushed instead of executing the script.

This semester in SBR700 I am working on it again and here is my rough plan for the semester.

Week 1- 3 - Working on resolving issues with viewsource python script displaying code instead of executing it (not as quick of a fix as many of you are probably thinking). By the end of week three I should have the issue resolved.
Week 4 + 5 - Cleaning up my spec file
Week 6 - Reviewing the guidelines for releasing and packaging in fedora and cleaning/modifying my packaging likewise
week 7+ - To be discussed.