Any Change in Helicon Config Editor Causes Incorrect Syntax

ISAPI_Rewrite is Apache mod_rewrite compatible URL rewriter for Microsoft IIS
User avatar
Posts: 7
Joined: 01 Apr 2012, 20:08

Any Change in Helicon Config Editor Causes Incorrect Syntax

02 Apr 2012, 18:27

If I open an htaccess file in the Helicon Config Editor and make any change and try to save it says that I have incorrect syntax and provides a list of every instruction with unknown expression beside it.

Even if I just select a line and hit the Comment Out key and then try to save I get errors for every line of code.

This file was copied from a linux server and I am trying to get this site to run on Windows IIS. Could there be something in the file that is causing this? Here are the contents of the file.


#
# Apache/PHP/Drupal settings:
#

# Protect files and directories from prying eyes.
<FilesMatch "\.(engine|inc|info|install|make|module|profile|test|po|sh|.*sql|theme|tpl(\.php)?|xtmpl)$|^(\..*|Entries.*|Repository|Root|Tag|Template)$">
Order allow,deny
</FilesMatch>

# Don't show directory listings for URLs which map to a directory.
Options -Indexes

# Follow symbolic links in this directory.
Options +FollowSymLinks

# Multiviews creates problems with aliased URLs and is not needed for Drupal.
Options -Multiviews

# Make Drupal handle any 404 errors.
ErrorDocument 404 /index.php

# Force simple error message for requests for non-existent favicon.ico.
<Files favicon.ico>
# There is no end quote below, for compatibility with Apache 1.3.
ErrorDocument 404 "The requested file favicon.ico was not found.
</Files>

# Set the default handler.
DirectoryIndex index.php index.html index.htm

# Override PHP settings that cannot be changed at runtime. See
# sites/default/default.settings.php and drupal_initialize_variables() in
# includes/bootstrap.inc for settings that can be changed at runtime.

# PHP 5, Apache 1 and 2.
<IfModule mod_php5.c>
php_flag magic_quotes_gpc off
php_flag magic_quotes_sybase off
php_flag register_globals off
php_flag session.auto_start off
php_value mbstring.http_input pass
php_value mbstring.http_output pass
php_flag mbstring.encoding_translation off
</IfModule>

# PHP 5.2.4
AddType x-mapp-php5 .php
AddHandler x-mapp-php5 .php

# Requires mod_expires to be enabled.
<IfModule mod_expires.c>
# Enable expirations.
ExpiresActive On

# Cache all files for 2 weeks after access (A).
ExpiresDefault A1209600

<FilesMatch \.php$>
# Do not allow PHP scripts to be cached unless they explicitly send cache
# headers themselves. Otherwise all scripts would have to overwrite the
# headers set by mod_expires if they want another caching behavior. This may
# fail if an error occurs early in the bootstrap process, and it may cause
# problems if a non-Drupal PHP file is installed in a subdirectory.
ExpiresActive Off
</FilesMatch>
</IfModule>

# Various rewrite rules.
<IfModule mod_rewrite.c>
RewriteEngine on

# Block access to "hidden" directories whose names begin with a period. This
# includes directories used by version control systems such as Subversion or
# Git to store control files. Files whose names begin with a period, as well
# as the control files used by CVS, are protected by the FilesMatch directive
# above.
#
# NOTE: This only works when mod_rewrite is loaded. Without mod_rewrite, it is
# not possible to block access to entire directories from .htaccess, because
# <DirectoryMatch> is not allowed here.
#
# If you do not have mod_rewrite installed, you should remove these
# directories from your webroot or otherwise protect them from being
# downloaded.
RewriteRule "(^|/)\." - [F]

# If your site can be accessed both with and without the 'www.' prefix, you
# can use one of the following settings to redirect users to your preferred
# URL, either WITH or WITHOUT the 'www.' prefix. Choose ONLY one option:
#
# To redirect all users to access the site WITH the 'www.' prefix,
# (http://example.com/... will be redirected to http://www.example.com/...)
# uncomment the following:
# RewriteCond %{HTTP_HOST} !^www\. [NC]
# RewriteRule ^ http://www.%{HTTP_HOST}%{REQUEST_URI} [L,R=301]
#
# To redirect all users to access the site WITHOUT the 'www.' prefix,
# (http://www.example.com/... will be redirected to http://example.com/...)
# uncomment the following:
# RewriteCond %{HTTP_HOST} ^www\.(.+)$ [NC]
# RewriteRule ^ http://%1%{REQUEST_URI} [L,R=301]

# Modify the RewriteBase if you are using Drupal in a subdirectory or in a
# VirtualDocumentRoot and the rewrite rules are not working properly.
# For example if your site is at http://example.com/drupal uncomment and
# modify the following line:
# RewriteBase /drupal
#
# If your site is running in a VirtualDocumentRoot at http://example.com/,
# uncomment the following line:
RewriteBase /

# Pass all requests not referring directly to files in the filesystem to
# index.php. Clean URLs are handled in drupal_environment_initialize().
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteCond %{REQUEST_URI} !=/favicon.ico
RewriteRule ^ index.php [L]

# Rules to correctly serve gzip compressed CSS and JS files.
# Requires both mod_rewrite and mod_headers to be enabled.
<IfModule mod_headers.c>
# Serve gzip compressed CSS files if they exist and the client accepts gzip.
RewriteCond %{HTTP:Accept-encoding} gzip
RewriteCond %{REQUEST_FILENAME}\.gz -s
RewriteRule ^(.*)\.css $1\.css\.gz [QSA]

# Serve gzip compressed JS files if they exist and the client accepts gzip.
RewriteCond %{HTTP:Accept-encoding} gzip
RewriteCond %{REQUEST_FILENAME}\.gz -s
RewriteRule ^(.*)\.js $1\.js\.gz [QSA]

# Serve correct content types, and prevent mod_deflate double gzip.
RewriteRule \.css\.gz$ - [T=text/css,E=no-gzip:1]
RewriteRule \.js\.gz$ - [T=text/javascript,E=no-gzip:1]

<FilesMatch "(\.js\.gz|\.css\.gz)$">
# Serve correct encoding type.
Header append Content-Encoding gzip
# Force proxies to cache gzipped & non-gzipped css/js files separately.
Header append Vary Accept-Encoding
</FilesMatch>
</IfModule>
</IfModule>

# $Id: .htaccess,v 1.111 2010/11/23 02:59:05 dries Exp $

User avatar
Posts: 1264
Joined: 07 Mar 2012, 10:16

Re: Any Change in Helicon Config Editor Causes Incorrect Syn

03 Apr 2012, 09:06

Hello,

There's nothing strange here. Most of the directives are not supported.

ISAPI_Rewrite is not Apache, though has 90% similar syntax for rewrite rules.

You may need to check the list of supported directives from our ISAPI_Rewrite documentation. In case you need to recreate all features from the provided .htaccess we strongly recommend to use HeliconApe(the best Apache emulator for Windows Server, especially for IIS7+). All Ape's documentation is provided here

Regards
Andrew

User avatar
Posts: 7
Joined: 01 Apr 2012, 20:08

Re: Any Change in Helicon Config Editor Causes Incorrect Syn

03 Apr 2012, 11:42

Thanks for the input Andrew. That was helpful to know. I posted on this other thread that I am relatively new to migrating a site from Linux to Windows IIS and so I am struggling with some of the fundamentals. The help I am getting on these forums is at least getting me pointed in the right direction.

Moving_Drupal_from_Linux_to_Windows_IIS-8-40.html?p=165#p165

User avatar
Posts: 1264
Joined: 07 Mar 2012, 10:16

Re: Any Change in Helicon Config Editor Causes Incorrect Syn

04 Apr 2012, 07:39

Anton is highly qualified specialist and will assist you in every possible way.

Regards
Andrew

User avatar
Posts: 7
Joined: 01 Apr 2012, 20:08

Re: Any Change in Helicon Config Editor Causes Incorrect Syn

04 Apr 2012, 11:15

Anton did solve my problems. Now that the crisis is over and the site is up for people to register for the conference I will study the code he sent and learn more about htaccess directives for IIS.

Have a great day!

Return to ISAPI_Rewrite 3.0

Who is online

Users browsing this forum: No registered users and 0 guests