Using Helicon ISAPI_Rewrite 3 looses form POST data

Hi,

I have the MODx CMS system installed on IIS6 and am using ISAPI_Rewrite 3 to enable Search Engine Friendly URLs.

The code I have works nicely to rewrite /index.php?id=2 etc. to say /friendly-name.htm.  Issue comes with Form POST data going missing on the login and contact forms.  The forms work correctly when Friendly URLs are disabled.  

The ISAPI_Rewrite 3 logfiles show no errors.

I've asked for help on the MODx Forum but have had no response in 3 days.  The Live HTTP Headers AddOn for Firefox shows the data being posted when a form is submitted but the resulting web page does not see the data.

Can anyone advise what I can do to figure where the POST data is going to and how to ensure it survives the ISAPI_Rewrite Process?

My httpd.ini file is below.

Thanks,

Chris


RewriteEngine On
RewriteCompatibility2 On
RepeatLimit 32
RewriteBase

# ensure any POST data is available after url is rewritten
RewriteCond %{REQUEST_METHOD} !^POST$ [NC]


#  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 ^/(?!(?:manager|assets)/)(.*)\.html(?:\?(.*))?$ /index.php?q=$1?2&$2: [NC,L,U]

Open in new window

vinylaAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Steve BinkCommented:
I have very little experience with  Helicon's filter, but my experience with IIS6 and PHP shows the exact same behavior.  The PHP bug is here:

http://bugs.php.net/38094

What I found when I looked into it was that IIS6 was mangling and/or removing the header data of the original request.  I'm not sure how this impacts Helicon since the filter could be taking over redirection.  If it allows IIS6 to redirect based on Helicon's decisions, then this issue will affect you in the same manner.  I eventually scrapped the project (an app conversion from LAMP to WIMP) because this issue could not be resolved.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft IIS Web Server

From novice to tech pro — start learning today.