I finally figured it out. I need to create a backend content server for the SSL module to talk to. Once I did that and reconfigured the ssl-proxy to acknowlege it, it began to work. Here is the final config:
!*********************** SSL PROXY LIST ***********************
ssl-proxy-list somedomain_list
description "SSL List for www.somedomain.com"
ssl-server 1
ssl-server 1 vip address 10.101.0.8
ssl-server 1 rsacert somedomain-ssl
ssl-server 1 rsakey somedomain-ssl
ssl-server 1 urlrewrite 1 test.somedomain.com sslport 443 clearport 80
ssl-server 1 cipher rsa-with-rc4-128-md5 10.101.0.8 81
active
!************************** SERVICE **************************
service somedomain_SSL
type ssl-accel
slot 2
add ssl-proxy-list somedomain_list
keepalive type none
compress enable
active
service www.somedomain.com_redirect
ip address 2.2.2.2
keepalive type none
type redirect
no prepend-http
redirect-string "https://test.somedomain.com"
active
service www01.somedomain.com
ip address 10.101.0.43
keepalive type http
protocol tcp
port 80
active
service www02.somedomain.com
ip address 10.101.0.44
keepalive type http
protocol tcp
port 80
active
!*************************** OWNER ***************************
owner www.somedomain.com
content www.somedomain.com_decrypt
vip address 10.101.0.8
add service www01.somedomain.com
add service www02.somedomain.com
protocol tcp
port 81
active
content www.somedomain.com_http
vip address 10.101.0.8
add service www.somedomain.com_redirect
protocol tcp
port 80
url "//test.somedomain.com/*"
active
content www.somedomain.com_https
protocol tcp
add service somedomain_SSL
vip address 10.101.0.8
application ssl
port 443
active
!*************************** GROUP ***************************
group www.somedomain.com_Servers
vip address 10.101.0.8
add destination service www01.somedomain.com
add destination service www02.somedomain.com
active
