Posted: 20 August 2008 at 8:07am | IP Logged

Hello,

We recently upgraded from version 2 to the full licensed version 3 and we noticed that our coldfusion generated cookies (CFID and CFTOKEN) were no longer passed to our client.  Other cookies however were being passed through yet it appears that ISAPI rewrite was specifically filtering these out.  Turning on the debug did not reveal any errors in the error or rewrite log.  Using a http header viewer showed that the cookies were not included in the header.  However when eliminating the rewrite tool the cookies are passed without issue.

I have seen a couple of posts with similar situations yet have not see any solutions offered.  Can someone offer any assistance?

Thanks,

Yolanda

Posted: 21 August 2008 at 7:47am | IP Logged

Here is what was captured in the rewrite.log when we debugged the other day:

71.35.213.55 71.35.213.55  Mon, 18-Aug-2008  12:34:45 GMT [192.168.2.81/sid#371995081][rid#19628552/initial] (2) init rewrite engine with requested uri /
71.35.213.55 71.35.213.55  Mon, 18-Aug-2008  12:34:45 GMT [192.168.2.81/sid#371995081][rid#19628552/initial] (1) Htaccess process request C:\Program Files\Helicon\ISAPI_Rewrite3\httpd.conf
71.35.213.55 71.35.213.55  Mon, 18-Aug-2008  12:34:45 GMT [192.168.2.81/sid#371995081][rid#19628552/initial] (3) applying pattern '^/httpd(?:\.ini|\.parse\.errors).*$' to uri '/'
71.35.213.55 71.35.213.55  Mon, 18-Aug-2008  12:34:45 GMT [192.168.2.81/sid#371995081][rid#19628552/initial] (3) applying pattern '^.*\.isrwhlp$' to uri '/'
71.35.213.55 71.35.213.55  Mon, 18-Aug-2008  12:34:45 GMT [192.168.2.81/sid#371995081][rid#19628552/initial] (3) applying pattern '^/(.*)$' to uri '/'
71.35.213.55 71.35.213.55  Mon, 18-Aug-2008  12:34:45 GMT [192.168.2.81/sid#371995081][rid#19628552/initial] (1) escaping http://192.168.2.184:80/
71.35.213.55 71.35.213.55  Mon, 18-Aug-2008  12:34:45 GMT [192.168.2.81/sid#371995081][rid#19628552/initial] (2) forcing proxy-throughput with /x.rwhlp?p=0
71.35.213.55 71.35.213.55  Mon, 18-Aug-2008  12:34:45 GMT [192.168.2.81/sid#371995081][rid#19628552/initial] (1) go-ahead with proxy request /x.rwhlp?p=0 [OK]
71.35.213.55 71.35.213.55  Mon, 18-Aug-2008  12:34:45 GMT [192.168.2.81/sid#371995081][rid#19628552/initial] (1) Rewrite URL to >> /x.rwhlp?p=0
71.35.213.55 71.35.213.55  Mon, 18-Aug-2008  12:34:45 GMT [192.168.2.81/sid#371995081][rid#19628552/initial] (2) rewrite '/' -> '/x.rwhlp?p=0'
71.35.213.55 71.35.213.55  Mon, 18-Aug-2008  12:34:45 GMT [192.168.2.81/sid#371995081][rid#19628552/initial] (2) internal redirect with /x.rwhlp?p=0 [INTERNAL REDIRECT]

Also here are our rules:

# Helicon ISAPI_Rewrite configuration file
# Version 3.1.0.54

RewriteEngine On
RewriteCompatibility2 On
RepeatLimit 32
RewriteBase
# unsupported directive: [ISAPI_Rewrite]

#  3600 = 1 hour
# unsupported directive: CacheClockRate 3600

RewriteLog "D:\Rewrite\rewrite.log"
RewriteLogLevel 9
LogLevel debug

#  Block external access to the httpd.ini and httpd.parse.errors files
RewriteRule ^/httpd(?:\.ini|\.parse\.errors).*$ / [NC,F,O]
#  Block external access to the Helper ISAPI Extension
RewriteRule ^.*\.isrwhlp$ / [NC,F,O]

RewriteRule ^/(.*)$ http\://192.168.2.184:80/$1 [NC,P]

Posted: 22 August 2008 at 8:01am | IP Logged

This is a test site without external access currently.  And yes these rules did work in ISAPI rewrite 2.  All I did was import them into the new product.

The goal of the rules is to proxy requests to an application pool (which we did test to ensure that the pool was properly retuning the cookie, by accessing the pool's ip directly).  However once the requests returns back up to the ISAPI rewrite proxy for some reason the specific cookie is being removed. 

I've seen a similar post that was made recently on the forum here.  If you were able to discover a solution for this problem it may be useful for my situation.

Thanks,

Yolanda