.htaccess style with SET
3 views
Skip to first unread message
J.T.
Mar 20, 2012, 1:06:18 PM3/20/12
to UrlRewrite
I would like to pass through a request or server value much like ISAPI
rewrite does for IIS. I can do this with a SET type=request in the
URLrewrite.xml. I already have several hundred rules setup in
an .htaccess file. Is there anyway to set a value using the htaccess
compatibility method or do I need to translate all those rules into
the urlrewrite.xml?
I have both pieces working separately but not together.
rewrite does for IIS. I can do this with a SET type=request in the
URLrewrite.xml. I already have several hundred rules setup in
an .htaccess file. Is there anyway to set a value using the htaccess
compatibility method or do I need to translate all those rules into
the urlrewrite.xml?
I have both pieces working separately but not together.
Avlesh Singh
Mar 21, 2012, 12:26:10 AM3/21/12
to urlre...@googlegroups.com
Unfortunately, we don't support the <set> behavior for mod_rewrite based rules. You have to switch to the XML version.
Thinking about it, does it make sense to write a simple contrib to parse the .htaccess file and create urlrewrite.xml once for people who intend to switch?
Cheers
Avlesh
--
You received this message because you are subscribed to the Google Groups "UrlRewrite" group.
To post to this group, send email to urlre...@googlegroups.com.
To unsubscribe from this group, send email to urlrewrite+...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/urlrewrite?hl=en.
J.T.
Mar 23, 2012, 1:40:15 PM3/23/12
to UrlRewrite
We were actually discussing this in the office. We all agree that
maintaining two config files introduces too much risk. One of us
suggested creating a widget that would parse our htaccess file into
XML for development and use it straight out in production. So, I think
it would be a great addition. However, there are issues of non-
compatibility to deal with. We weren't sure of a graceful way to
handle it.
On Mar 21, 12:26 am, Avlesh Singh <avl...@gmail.com> wrote:
> Unfortunately, we don't support the <set> behavior for mod_rewrite based
> rules. You have to switch to the XML version.
>
> Thinking about it, does it make sense to write a simple contrib to parse
> the .htaccess file and create urlrewrite.xml once for people who intend to
> switch?
>
> Cheers
> Avleshhttp://webengage.com
maintaining two config files introduces too much risk. One of us
suggested creating a widget that would parse our htaccess file into
XML for development and use it straight out in production. So, I think
it would be a great addition. However, there are issues of non-
compatibility to deal with. We weren't sure of a graceful way to
handle it.
On Mar 21, 12:26 am, Avlesh Singh <avl...@gmail.com> wrote:
> Unfortunately, we don't support the <set> behavior for mod_rewrite based
> rules. You have to switch to the XML version.
>
> Thinking about it, does it make sense to write a simple contrib to parse
> the .htaccess file and create urlrewrite.xml once for people who intend to
> switch?
>
> Cheers
Avlesh Singh
Mar 23, 2012, 1:43:50 PM3/23/12
to urlre...@googlegroups.com
Please create a ticket and consider contributing your "htaccess to xml parser" as a patch. I am tempted to think that it might be a good contrib.
Cheers
Avlesh
J.T.
Mar 23, 2012, 2:06:18 PM3/23/12
to UrlRewrite
Avlesh,
I'm not sure if we will be taking this route to make a contribution.
We had high hopes for this solution, but we are fairly dug in with
ISAPI_rewrite, so our hands might be tied.
On Mar 23, 1:43 pm, Avlesh Singh <avl...@gmail.com> wrote:
> Please create a ticket and consider contributing your "htaccess to xml
> parser" as a patch. I am tempted to think that it might be a good contrib.
>
> Cheers
> Avleshhttp://webengage.com
I'm not sure if we will be taking this route to make a contribution.
We had high hopes for this solution, but we are fairly dug in with
ISAPI_rewrite, so our hands might be tied.
On Mar 23, 1:43 pm, Avlesh Singh <avl...@gmail.com> wrote:
> Please create a ticket and consider contributing your "htaccess to xml
> parser" as a patch. I am tempted to think that it might be a good contrib.
>
> Cheers
Reply all
Reply to author
Forward
0 new messages