Wildcard host SSL URL rewrite

I'm working on setting up a URL rewrite that will work for all hosts of a specific domain. I could just do a ".*" in the action-list, but the business unit has requested that I restrict the rewrites to just URLs served up containing a particular domain and all of its various hosts. Would the action-list below work for *.blah.com? Like www.blah.com, apps.blah.com, etc? Thanks.
action-list type modify http blah-urlrewrite
ssl url rewrite location ".*\.blah\.com"

Hi,
That rewrite should do the trick
Cesar R
ANS Team

Similar Messages

SSL URL REWRITE SYNTAX

Hi team.
I'm trying to write a SSL URL REWRITE expression but it doesn't work.
Imagine that I wuold write a location that covers:
www.cisco.com
www1.cisco.com/new
www.2.cisco.com/old
web.cisco.com
the fixed part here is ".cisco.com" and the headers and trailer can vary.
The experssion I wrote and doesn't work is:
.*\.cisco\.com
What I'm doing wrong?
Thank you!!

Hi David,
.*\.cisco\.com will match www.cisco.com and web.cisco.com but it will not match www1.cisco.com/new because "/". If you do .*\.cisco\.com/ then it will match www1.cisco.com/new and www.2.cisco.com/old but not www.cisco.com and web.cisco.com. I just tried that in regex builder. You can try that too. You can use .*cisco.com.* i.e wild cards both at begining and end. That should match everything before and after cisco.com.
Regards,
Kanwal

ACE module SSL url rewrite and path rewrite

Hi all,
I'm hoping some of you helpful people on this forum can guide me or suggest a solution to a problem I'm faced with.
I am currently load balancing exchange 2010 traffic via an ACE module. Software version is A2(3.3). I have most parts of it working fine however I am having an issue when it comes to SSL termination for Outlook Web Access (OWA).
The problem comes down to a HTTP header (field is location). I have configured an action list to re-write the SSL pure URL as per page 96 of the "Cisco Application Control Engine Module SSL Configuration Guide". example:
ssl url rewrite location bnecas\.mycompany\.com sslport 443
That part works, the http header location field that comes back from the GET request is changed to https://cas.mycompany.com which is great. However, in addition to that url, there is also a path or something following that part. The actual string that is returned is:
https://cas.mycompany.com/owa/auth/logon.aspx?url=http://cas.mycompany.com/owa/&reason=0
The first bit of it, (https://cas.mycompany.com) is changed by the ssl url rewrite command, however the last part (http://cas.mycompany.com/owa/&reason=0) isn't changed.
This is where I've been trying to get the http Header Rewrite command to do something. I don't know if it can work in conjunction with the ssl url rewrite function however with the ssl rewrite function it seems it can't change bits of the string that aren't the pure URL at the front.
The end result is that while I have an SSL connection to the OWA login page, when I do login to OWA it reverts back to HTTP. I'm fairly sure it is because of the last part of the location string above. Is there a way to change that location string to do the following:
1. change the first part of the string to be https://cas.mycompany.com (like the ssl url rewrite function)
2. change the last part of the location string to put https in there instead of http
Ideally I would love to have this string
http://cas.mycompany.com/owa/auth/logon.aspx?url=http://cas.mycompany.com/owa/&reason=0
replaced with this one
https://cas.mycompany.com/owa/auth/logon.aspx?url=https://cas.mycompany.com/owa/&reason=0
I had originally tried the following in the action list:
header rewrite response location header-value "(owa/auth/logon\.aspx\?url=)http(://bnecas\.thiess\.aus/owa/&reason=0)" replace "%1https%2"
ssl url rewrite location bnecas\.mycompany\.com sslport 443
but it didn't work. I'm probably screwing up the regex somewhere however there doesn't seem to be very clear examples anywhere I can find.
Any help will be greatly appreciated and of course I will be sure to rate every post that responds to my plea for help.
Brad

Hi Brad,
try this:
/* Style Definitions */
table.MsoNormalTable
{mso-style-name:"Table Normal";
mso-tstyle-rowband-size:0;
mso-tstyle-colband-size:0;
mso-style-noshow:yes;
mso-style-priority:99;
mso-style-qformat:yes;
mso-style-parent:"";
mso-padding-alt:0in 5.4pt 0in 5.4pt;
mso-para-margin:0in;
mso-para-margin-bottom:.0001pt;
mso-pagination:widow-orphan;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
mso-ascii-font-family:Calibri;
mso-ascii-theme-font:minor-latin;
mso-fareast-font-family:"Times New Roman";
mso-fareast-theme-font:minor-fareast;
mso-hansi-font-family:Calibri;
mso-hansi-theme-font:minor-latin;
mso-bidi-font-family:"Times New Roman";
mso-bidi-theme-font:minor-bidi;}
action-list type modify http X
header rewrite response Location header-value "http://(.*url=)http://(.*)" replace "https://%1https://%2"
we wont be using ssl url rewrite in this case
Also we will be needing persistence rebalance applied through application parameter map and apply that under the VIP class

Server 2012 R2 essentials url rewrite to exchange 2013 breaks remote web workplace

Hi all
Have a server 2012 r2 with essentials experience installed and an exchange 2013 sp1 on a member server.
I have 2 certificates
remote.domain.com for the essentials rww
mail.domain.com for exchange owa
I have added the administrator account to enterprise admins and have joined the exchange server with the essentials connector, so it appears on the dashboard.
Both certificates are installed correctly.
I have installed ARR 3.0 and created a serverfarm mail.domain.com and accepted that it created url rewrite for me.
Server farm does not have ssl offload enabled.
The url rewrite is setup like this:
Requested url: matches pattern, Using: Wildcards, Pattern *
Conditions: Match All, Input: HTTPS, Type: Matches the pattern, Pattern: ON
Action: Route to server farm
Scheme: https://, Server farm: mail.domain.com, Path: /{R:0}
Stop processing of subsequent rules: checked
Now pointing protokol 443 til the IP of the essentials server and navigating to https://mail.domain.com/owa brings the owa logon page with my trusted server certificate and all.
Everything works fine.
If I then navigate to https://remote.domain.com/remote then the webpage should show the login to the essentials remote web workplace.
But instead it shows a some what crippled version, like forms and pictures missing and it is obviously not working.
Trying to troubleshoot i changed the url rewrite from wildcards to exact match and put owa into the pattern field.
Then my remote web workplace showed up correctly with the matching certificate and all was fine.
But now owa shows a 404 directory not found.
I guess I need some help on this.
Somehow that server farm and the url rewrite, messes up my default website, with the remote site.
Much appreciated...
\Lars

Lars,
RE-Run the WSE wizard to reset the Internet settings.
Remove ARR and URLReWrite.
Once removed reboot.
Install ARR and URLReWrite again by downloading.
Do NOT configure any farm settings.
Use the ARRConfig utility that comes with WSE:
http://technet.microsoft.com/en-us/library/jj200172.aspx
That TN page explains how to run the utility. Make sure you have exported the mail certificate including Public Key and Extended Properties first.
Philip Elder Microsoft Cluster MVP Blog: http://blog.mpecsinc.ca

Using URL Rewrite for HNSC Web App

Greetz!
I'm using host named site collections in my deployment of 2013 Enterprise. I've got a single web app, on the default zone, that was created on port 443 with the -SecureSocketLayer parameter. How can I seamlessly redirect users accessing a HNSC with http
to the correct (and only) https url? I'm using the URL Rewrite 2.0 with IIS 8.5.
I have the following rule in place but it is still throwing a 404 on pages. Is this able to work with Host Named Site Collections and does it matter that I've installed the Web App on 443 without having it on 80 first? It shouldn't but SharePoint has
surprised me before ;):
<rule name="SSL Redirect" enabled="true" stopProcessing="true">
                <match url="(.*)" />
                <conditions>
                    <add input="{HTTPS}" pattern="off" />
                </conditions>
                <action type="Redirect" url="https://{SERVER_NAME}" redirectType="Found" />
            </rule>
        <rule name="HTTP/S to HTTPS Redirect" enabled="false" stopProcessing="true">
          <match url="(.*)" negate="true" />
            <conditions logicalGrouping="MatchAny">
                    <add input="{SERVER_PORT_SECURE}" pattern="1" />
                    <add input="{SERVER_PORT_SECURE}" pattern="0" />
     </conditions>
     <action type="Redirect" url="https://{HTTP_HOST}" redirectType="Permanent" />
     </rule>
Love them all...regardless. - Buddha

are you using the URL Rewrite on the same IIS web application as the SharePoint sites?
Scott Brickey
MCTS, MCPD, MCITP
www.sbrickey.com
Strategic Data Systems - for all your SharePoint needs

IIS Reverse Proxy with URL rewrite.

Hi all, hoping to leverage the wealth of knowledge contained here.
Any assistance would be very welcome.
I'm having an issue getting a reverse proxy and URL rewrite working in IIS 7.0.
I need to redirect all requests with a specific virtual directory suffix only.
ie; https://domain.test.com/outbound/Content/query_etc
With /Outbound/ being the trigger.
This should be redirected to http://10.10.10.10/inbound/Content/query_etc
While at the same time, requests without the /outbound/ suffix should be handled locally.
I have configured the reverse proxy as described in a few articles, and have had no luck.
Here's a snippet from my (sanitized) web.config at the site level.
<rewrite>
<outboundRules>
<rule name="ReverseProxyOutboundRule1" preCondition="ResponseIsHtml1">
<match filterByTags="A" pattern="^http(s)?://10.10.10.10/inbound/(.*)" />
<action type="Rewrite" value="https://domain.test.com/outbound/{R:2}" />
</rule>
<preConditions>
<preCondition name="ResponseIsHtml1">
<add input="{RESPONSE_CONTENT_TYPE}" pattern="^text/html" />
</preCondition>
</preConditions>
</outboundRules>
<rules>
<rule name="ReverseProxyInboundRule1" stopProcessing="true">
<match url="^outbound/(.*)" />
<action type="Rewrite" url="http://10.10.10.10/inbound/{R:1}" appendQueryString="true" logRewrittenUrl="false" />
</rule>
</rules>
</rewrite>
To me, this looks correct, yet it doesn't work.
With this, I get the normal 404 - Error Code 0x80070002, with the text indicating the local directory doesn't exist, so.... not being picked up by the filter for redirection.

Hi Andrew,
Looking at your requirements it appears you need Reverse Proxy To Another Site/Server.
By using URL Rewrite Module together with
Application Request Routing module you can have IIS 7 act as a
reverse proxy.
It seems like URL Rewrite can't re-route the request somewhere else out of the server.
Even when you rewrite the url the actual connection remains with the server. Hence if your original server doesn't have /inbound/Content/query_etc it will fail with 404.
Hosting multiple domain names under a single account using URL Rewrite.
It’s a common desire to have a single IIS website that handles multiple sites with different domain names.
References:
How to create a url alias using IIS URL Rewrite:
http://blogs.technet.com/b/mspfe/archive/2013/11/27/how-to-create-a-url-alias-using-iis-url-rewrite.aspx
Reverse Proxy with URL Rewrite v2 and Application Request Routing:
http://www.iis.net/learn/extensions/url-rewrite-module/reverse-proxy-with-url-rewrite-v2-and-application-request-routing
Regards,
Satyajit
Please“Vote As Helpful”
if you find my contribution useful or “MarkAs Answer” if it does answer your question. That will encourage me - and others - to take time out to help you.

URL rewriting for a WebService Consumer Proxy

Hi all,
Did anybody come across this issue?
I have a SAP System - let's call it "TM" - that I want to bind with another non-SAP one - let's call it "FB" - without any PI between them.
The communication is made as a Service Consumer (TM side), the Proxy (see image below) and Proxy-Implementation Class being generated automatically after the ".wsdl" file and the "url" given by the documentation of FB.
Everything looks good! All the Methods (operations) that are available from the service have been added to the Implementing Class.
After the Proxy generation, I also created the Logical Port (in transaction SOAMANAGER - see image below) where the path, host, prefix, and all the necessary stuff were also automatically created after the ".wsdl" document.
So far so good! When I want to test it and to play along with this connection TM -> FB, I am creating the Proxy-Object, I am filling the required User / Pass / and an ID in order to call the first method. As you have probably guessed already: LOGIN.
    ls_in_login-login_request-id             = '...some ID...'.
    ls_in_login-login_request-user          = '...some user ...'.
    ls_in_login-login_request-password = '...some password'.
TRY.
         CREATE OBJECT lo_proxy
           EXPORTING
             logical_port_name = 'ZAS_PORT_FB'.
     CATCH cx_ai_system_fault INTO lo_ref.    " Application Integration: Technischer Fehler
ENDTRY.
   TRY.
       CALL METHOD lo_proxy->login
         EXPORTING
           input = ls_in_login
         IMPORTING
           output = ls_out_login.
     CATCH cx_ai_system_fault INTO lo_ref.    " Application Integration: Technischer Fehler
     CATCH cx_ai_application_fault INTO lo_ref.    " Application Integration: Applikations Fehle
ENDTRY.
As a response, (meaning that the connection works and that the WebService acknowledges the connection) I get a "SessionID" -> a string of characters.
In the Wiki of the Service is written that from this point on, every other methods (but I mean ALL of them, logout() also...) need to be called along with this SessionID. The problem is, that this SessionID doesn't have a specific place in the "inbound"-structure of the methods, but this mechanism of passing around the SessionID must be made with URL rewriting. Another solution would be to use COOKIES. From my point of view, a so-called URL rewriting would be easier, right?
In the documentation is the following info written:
URL rewriting (recommended):
The JSessionId is attached to the URL of the SOAP request, as follows: http://[URL];jsessionid=[jsessionid]
Caused by tecnical reasons, it is necessary to specify the static string “;jsessionid=” in lower case letters.
I have turned this "LO_PROXY" object around and around and around... trying to find a solution... a method...anything that would let me rewrite the URL, but nothing...
I have also tried to use ce CL_HTTP_CLIENT class and to create myself the client and the URL and the host and everything manually... but in this case how do I end up in calling a specific "custom" method -> for instance... how do I call the "LOGIN"... or the LOGOUT...where do I put the parameters, etc?
Do you have any suggestions / ideas / hints ?
Thanks a lot in advance!
Warm regards,
Alex

Hi Stefan,
You are right! It doesn't support to set URL / HTTP parameters outside the logical port.
Nevertheless, I have debugged the whole engine and found out that via custom coding (enhancements / modifications) and with extreme attention, the URL can be rewritten as desired.
When a method of the proxy is called, let's say for instance: lo_proxy->logout (...) - as written up for example, the method CL_HTTP_CLIENT=>CREATE_BY_URL is called dynamically.
In this method, in the "url" variable is the desired URL that needed to be rewritten.
Here it's about an importing parameter, so it cannot be changed so easily, but it's not impossible.
Another place where a nice Enhancement can be created is at the beginning of the FM "SWLWP_URI_PARSE".
You need to be very careful not to change these places in all cases (this CREATE_BY_URL will be called pretty much), JUST when the specific conditions are fulfilled.
Have a great day / week!
Warm regards,
Alex

URL Rewrite Rules in 10.1.4

Hi,
I am having some trouble rewriting the urls, I can't make it work ...
What I want is to change the url:
http://www.mycompany.com/portal/page/portal/portal_sverige/
to
http://www.mycompany.com/sverige
Where "portal_sverige" is the page group.
What I did was:
Configure the properties in the page group:
Search pattern: /portal/page/portal/portal_sweden/
Replace pattern: /sweden/
And I went to enterprise manager, MT, http server, administration, advanced server properties, httpd.conf, and put in the lines:
RewriteEngine On
RewriteRule ^/sweden/(.*)$/portal/page/portal/portal_sweden/$1 [PT]
However, when I try to use navigator to edit a page in that group, I get:
http://www.mycompany.com/sweden/pagename?_mode=16
Returns:
Object not found. (WWC-50003)
And just typing in www.mycompany.com/sweden returns 404 error instead of the root page as I would have liked.
Any ideas about what to do? I can't really find any information ... is the change made in the MT ? IM ? Do I have to do it in some specific order? Is the syntax wrong?
Appreciate any help, thanks

Hello Sayeeas,
I posted an answer to this question a couple months back... check out the thread
Re: Portal URL Rewrite
Here is the answer:
In this example the name of the page group is "www":
Our rewrite rule is also set up in a virtual host section of the httpd.conf file as well so some of the options may not be required for your set up:
RewriteEngine on
RewriteOptions inherit
RewriteCond %{REQUEST_URI} !^/(portal|pls|images).*$
RewriteRule ^(.+) /portal/page/portal/www$1 [PT]
The rewrite condition allows us to ignore the rewrite for certain items in the path. This allows the portal navigator to work. There may be a couple more items that need to be added to the condition because I recently noticed that the help pages dont function properly.
In the portal configuration for the rewrite rule we specify:
Search pattern: /portal/page/portal/www
Replace pattern:
Thats right, the replace pattern is blank.
To see it in action check out http://www.sagelogix.com
-sean
Solutions Architect
http://www.sagelogix.com

Using Tomcat URL rewrite valve

http://tomcat.apache.org/tomcat-8.0-doc/rewrite.html
Looks like the latest version of Tomcat has added support for URL rewriting similar to Apache mod_rewrite
I can't seem to find any documentation other than the page above.
Has anyone used this to, for example, rewrite APEX URLs from http://host:port/apex/... to http://host:port/pls/apex ? Where should we put the RewriteCond and RewriteRule directives?
Thanks

I just went though this, spent about two days trying to figure out how to do with only tomcat and gave up. I found and used urlrewrite.. The instructions are right on main page but are vague. I've given "hints" below. My info assumes you renamed ords.war to apex.war.   I tried to post full details of my exploits/trials/troubles using the Oracle blog but it errored out.
http://tuckey.org/urlrewrite/
Step 1 say to place the file in WEB-INF/lib. For Tomcat, WEB-INF is the Tomcat application directory, mine was /opt/apache-tomcat-7.0.56.   Place in the <tomcat_app_dir>/lib directory.
Step 2 says to edit the web.xml file, adding the config text for urlrewrite. This file is located in <tomcat_app_dir>/ROOT/WEB-INF Copy text and paste just above the </web-app> tag at the bottom of the <tomcat_app_dir>/ROOT/WEB-INF/web.xml file.
Step 3 talks about editing urlrewite.xml file, which doesn't exist. You must create this file, in the same directory, <tomcat_app_dir>/ROOT/WEB-INF. The following is the contents of mine.
<urlrewrite use-query-string="true">
                <note>
                 rewrite from /pls/apex to pls
                </note>
       <rule>
            <from>/pls/apex/f\?p(.*)</from>
            <to type="redirect">/apex/f?p$1</to>
        </rule>
</urlrewrite>
You can check that urlrewite is working by accessing the admin/test page from the localhost....<servername>:8080/rewrite-status. The page shows you the rule and what it thinks it's going to do.
You now need to restart Tomcat and your old URL <servername>/pls/apex should work for your users who have bookmarked your old apex apps. It works for the new URL as well: <servername>/apex
I noticed you are also referencing port numbers in your sample url. Take a look at this blog post below, specifically step 6 and 7 to learn how to redirect to 80, so you don't have to use a port.
Install Tomcat 7 on CentOS, RHEL, or Fedora : David Ghedini

Web dispatcher url Rewritting to several sap systems

Hello SAP NW Community,
we need a reverse Proxy to achieve application of different SAP System via Internet. We desided to use web Dispatcher.
The host names of sap systems should not be visible, because of this we create the following URL Rewritting rules.
For example:
AAA, BBB and CCC are sap System SIDs;
"wdisp.company.com" is the FQDN fron webdispatcher
The "icm_filter" Looks like this:
if% {HTTP_HOST} RegIMatch "wdisp.company.com"[and]
If% {PATH} RegIMatch "AAA"
RegIRewriteUrl ^/AAA/(.*) /$1 [noescape]
SetHeader x-sap-webDisp-target-sid AAA [break]
the next rules are the same but for BBB and CCC.
The idea is to rewrite in background all URLs such as:
http(s)://wdisp.company.com/AAA/...
to :
http(s)://<FQDN from AAA>/...
The result is always the same: the rewritting for AAA works fine but for BBB and CCC we get -http error 404.
The results are independent from web browser(IE or Firefox).
The http trace Tools- HttpWatch Basis or Firebug show also no rewritting for BBB und CCC.
According the documentation is web Dispatcher able to support many "stateful" and "stateless" connection to different backend sap System.
Do you have any ideas why the rewritting works only for the first sap System?
We tested with different browser and Browser sessions but the resul was the same.
BR,
Rumen

Hi,
Instead of PATH , use different pots like this, you can get the URL redirection,
icm_filter.txt :
if %{HTTP_HOST} regimatch wdhost.company.com*
SetHeader x-sap-webdisp-target-sid AAA [break]
if %{HTTP_HOST} regimatch wdhost.company.com*
SetHeader x-sap-webdisp-target-sid BBB [break]
if %{HTTP_HOST} regimatch wdhost.company.com*
SetHeader x-sap-webdisp-target-sid CCC [break]
In Instance profile :
wdisp/system_0 = SID=AAA,MSHOST= AAA.HostNane ,MSPORT=8111
wdisp/system_1 = SID=BBB,MSHOST= BBB.Hostname ,MSPORT=8100
wdisp/system_2 = SID=CCC,MSHOST= CCC.Hostname ,MSPORT=8101
URL :
http://wdhost.company.com:8111 --- goes to AAAhost and so on.
regards
Vagesan

IIS Url Rewriting supported with SharePoint 2010?

I am currently working for a client that is investigating how they can do vanity domain names for sub sites. I don't believe this will actually work with SharePoint 2010 and believe it may put the environment in an unsupported state...however I need
to find some sort of official MS statement saying so.
Everything I find points me to
http://technet.microsoft.com/en-us/library/cc261814%28office.12%29.aspx#section2 which states that "Windows SharePoint Services 3.0 does not support asymmetrical paths" however I can't find anything that says the equivalent for 2010.
I know that web apps and AAM are the typical approaches, and now in 2010 you can do host named site collections, however they want to do sub-sites.
Can anyone point me to any official MS statement stating that this is not support with SharePoint 2010?
Tony Testa www.tonytestasworld.com

We ran into the same question. Since there's no official statement from Microsoft to be found on the internet that takes away the rumors about it being supported, we set out the question with Microsoft to provide their official statement. Their
reply was that URL rewriting is supported. Find the full reply from Microsoft at my website at
https://www.zomers.eu/knowledge/sharepoint2010/Pages/Url-rewriting-is-supported-for-SharePoint-2010.aspx
This link doesn't work and also directly contradicts statements from other Microsoft sources, e.g.
http://blogs.msdn.com/b/opal/archive/2010/04/23/sharepoint-2010-search-engine-optimization-seo-tips.aspx
where the following is stated:
"URL Rewriting is still not supported - however url redirect is supported. We are using url redirect feature in url rewrite model."
Please provide a link that works and/or back up your claim. Thanks.

Cookies, URL-Rewriting, and Sessions

Hi All,
I am aware that this is probably a question that has been asked many times in the past. Nonetheless, I have not been able to fully comprehend the differences. Therefore I would appreciate it, if someone could kindly spend some time explaining the differences between the three and when each would be the most preferred solution. ( cookies, url rewriting and sessions )
So far what I understand is that, cookies can be used to store small amounts of data not more than 4kb, and that most browsers can not accept more than 20 at a time.... but would it be correct to say that the data is stored within the http headers ?
URL rewriting, on the other hand is a method which can be used if cookies have been disabled by a browser. The 'session id' is appended to the url, and used to remember the data. ( how ? ). Although, it does mean that the programmer has to be very careful and ensure that rewriting occurs everytime it is passed to the browser, including redirection. ( whatever that means ? )
Http sessions, seem to be the best solution out of the three ( but if this is the case, why are cookies and rewriting still hanging around today ? And even being taught at universities ? ). Also, they work on top of cookies and if these have been disabled sessions will not work !! ....
As you can see ( from the above ) I do not have a thorough understanding of the three methods, especially if it comes to specifying the differences between the three.
I would appreciate an explanation.

HttpSessions use cookies or url rewritting to pass the session id which the server uses to associate a particular session with a particular request. A well developed web application will be written to use url rewriting when a client has cookies disabled. That being said I yet to see such a web application and personally believe that few people still disable cookies.
Cookies still have uses.
Persistant cookies are used to store data that needs to persist between sessions. This data is stored by the browser in a text files and passed to the server in the header. An example of this would be a site that offers personalization would store the user's id so that each time the user accesses the site he would see his personalization without being required to log in. Yahoo is a good example.
In memory cookies are stored in the browser's memory and is used to store temporary data that goes away when the browser closes. Again this data gets passed to the server in the headers. Temporary cookies can be used to pass data between seperate web applications runing on the same host where storing the data in the session will not because each application has it's own session.

If ACE4710 supports URL rewrite?

Hello,
We just started testing this brand new ACE4710 with the latest software version 1.8. It seems this box does not support URL rewrite while the ACE blade with software A2.0 does. So the question is if someone has idea URL rewrite feature will be inplemented for ACE4710 and if yes when?

You got it all wrong :).
ACE module doesnt support "URL rewrite". You can rewrite the HTTP header like the host field but not the URL.
you can accomplish this on the ACE Appliance with the 'urlmap scope' command.
Page 2-14 of the "Application Acceleration and Optimization Configuration Guide" for the 4710 has more info.
Hope it helps
Syed

Name in certificate `URL' does not match host name `URL'

Hello,
We are getting the error
Name in certificate `URL' does not match host name `URL'?
Can someone can provide solution to resolve the above error? Also can you please inform whether Coldfusion 8 supports checking the Subject Alternative Names in the SSL certificate? If so, kindly tell us how to do it.
Environment that we use is coldfusion 8 with sql server 2005 (DB). If you have any query please let me know.
Thanks,
Satheesh.

Hi Siva,
we have faced the same problem on our application. To overcome this we used the below workarround...
Make the host entry for webservice provider [serviceprovider.test.com] pointing to its IP [172.99.71.12].
In cfm file
There's no need to add the proxy and the port in the cfm file.
             <cfhttp method="Post" url="#WEBSERVICE_SERVICE_PROVIDER#" resolveurl="Yes">
                <cfhttpparam type="Formfield" name="xmlValue" value="#tostring(xml)#">
            </cfhttp>
The below URL will help you on debugging CFHTTP Request
http://kb2.adobe.com/cps/998/9987e902.html

WAF url rewriting

Hi everyone,
can anyone tell me if the ACE Web Application Firewall can do a url rewriting?
I mean i have the followinf scenario:
the client connects to the WAF with https://c.cgi and the WAF do the ssl-offload and sent to the real server just the http://c.cgi request. This will make the real server to send back to the client a redirection url: http://b.cgi and i need that this url to be modified by WAF in a way that the client should see: https://b.cgi.
Any ideeas?
Thanks

Thanks ebreniz.
Sorry for the delay, but i was very busy (and still am).
I do not understand (i am very far from being a programmer) the syntax of what you've wrote.
And, if you can tell me, where in the Web Interface of the WAF should i configure that?
where can i find the "About the Quick Pattern" section?
Thanks for your reply and i hope i am not too "profane" about the topic.
Costin

Wildcard host SSL URL rewrite

Similar Messages

Maybe you are looking for