I have an Oracle Apex installation.
Apex is working fine through ip address : xx.yy.xx.yy:8080
I would like to access my application from my custom domain.
I installed IIS on my windows 10 server and I changed the DNS entries to route requests on my domain to the server ip address.
In my index.html file I added the following line :
<meta HTTP-EQUIV="REFRESH" content="0; url=http://xx.yy.xx.yy:8080">
The redirection woks but I have an ugly URL with the port number.
Does anyone know how to keep the domain name and get rid of the port number ?
(I can't change the port 8080 since it's the default port used by Apex)
Thanks.
Cheers,
You can create another site and make sure it can be accessed via 8080.
1.Please install ARR&URLrewrite and ensure IIS manager->server node-> application request routing cache->server proxy settings->Enable proxy
2.Create a website with 80 port and make sure it can be accessed from http://xx.yy.xx.yy
3.Create URL rewrite rule like. You may need to modify this rule based on your requirement
<rule name="rewrite">
<match url="(.*)" />
<conditions>
<add input="{SERVER_PORT}" pattern="80" />
</conditions>
<action type="Rewrite" url="http://xx.yy.xx.yy:8080/{REQUEST_URI}" />
</rule>
4.Please modify <meta HTTP-EQUIV="REFRESH" content="0; url=http://xx.yy.xx.yy:8080"> to http://xx.yy.xx.yy">
Now when you access the web page.
Your page->redirect to http://xx.yy.xx.yy->URL reverse proxy rewrite to http://xx.yy.xx.yy:8080
Related
Unable to get URL rewrite to work.
http://my.domain/sso/my_app => http://my.domain:81/my_app
It doesn't have to be complicated, right ?
http://my.domain:81/my_app displays the expected page.
Here is the rule:
<rewrite>
<globalRules>
<rule name = "Laravel secure on port 81" enabled = "false" patternSyntax = "ECMAScript" stopProcessing = "true">
<match url = "sso /(.*)" />
<action type = "Redirect" url = "http://localhost:81/{R:1}" appendQueryString = "true" />
</rule>
</globalRules>
</rewrite>
I am testing on the IIS server itself http://localhost/sso/mon_app : no redirect, connection failed.
I tried with Application Request Routing by activating the proxy, by checking or not "Use URL Rewrite to inspect incoming requests".
By checking, it creates a redirect rule that I adapted :
<rule name = "ARR_server_proxy" enabled = "true" patternSyntax = "ECMAScript" stopProcessing = "true">
<match url = "* sso / *" />
<action type = "Rewrite" url = "http://localhost:81/{R:1}" />
</rule>
Nothing to do, it does not work.
No log in Failed Request.
I have no more idea.
Thanks, you help me to find the error : it's the port number.
I didn't know that the port 81 is forbidden in my office.
After some other tests with the port 8080, it's OK.
Enable proxy is checked in ARR.
Use URL Rewrite to inspect incoming requests isn't checked in ARR.
The rule stays in the server level with the port 8080
<rule name="Laravel secure on port 8080">
<match url="sso/(.*)" />
<action type="Rewrite" url="http://my.domain:8080/{R:1}" />
</rule>
Did you check the enable proxy on ARR? Reverse proxy only can work when proxy has been enabled.
I think there are some points which make the redirect failed.
The rule Laravel secure on port 81 should be add at site level not server level. Reverse proxy is to proxy the request sent to one site to another site, instead of proxying the request as soon as the request is sent to the server (the request has not been sent to any site).
The rule ARR_server_proxy doesn't have () in match url. So {R:1} always null.
In summary, you juest need to remove this rule to default site(or any other site which bind to http://mydomian). Request can be sent to default site first. The url match the rule and ARR proxy it to http://my.domain:81/my_app.
If it still fail, please use failed request tracing to troubleshoot url rewrite.
I want to add a path mysite.com/_this when a request for this path is called I want to serve the json file that's under Sites/MySite/Content.
The caveat is I cannot implement this via code change. I need a way to implement this setup using the IIS CLI.
I have found the following article https://learn.microsoft.com/en-us/iis/extensions/url-rewrite-module/iis-url-rewriting-and-aspnet-routing, but it's a little cryptic and hard to follow.
Windows: Window Server 2016 (1607)
IIS: 10.0.14393.0
In my opinion, the right solution for your issue is iis URL rewrite module.
If you did not install the url rewrite module you could download from the below link:
URL Rewrite
then add a rule in web.config file:
<rule name="Json Redirect" stopProcessing="true">
<match url="([\S]+[.](json))" />
<action type="Rewrite" url="folderpath/{R:1}" />
</rule>
You can do all these changes in the IIS Manager UI, but if you want to script them, look into the PowerShell IIS cmdlets.
I'm trying to do a URL rewrite on a certain path on my site that contains the child app in the path. The issue is that when I have the name of my child app in the path, the rule gets skipped.
So I have the current IIS setup:
Root App (example.com)
|
|---Child App (mychild)
Let's say the site is http://example.com
I can access the child app via http://example.com/mychild/...
Now I need to make a URL rewrite rule that will catch a specific URL that's under the child app. So for example this would need to be matched:
http://example.com/mychild/folder1/method1 and rewritten to something else
When I put this rule in (the root site web.config) however (regex removed for simplicity), the rule is not triggered, it continues to route to the child app, and results in a 404:
<rule name="rule1" enabled="true" patternSyntax="ExactMatch" stopProcessing="true">
<match url="mychild/folder1/method1" />
<action type="Rewrite" url="http://otherlocalserver"
</rule>
If I change the mychild instance in the url attribute to something else (that's not a child app), like:
<match url="hello/folder1/method1" />
This: http://example.com/hello/folder1/method1 will match.
How can I get this rule to apply before IIS thinks that I want it to use the child application?
Is the child app running as a seperate website?
Then you should do the rewrite path in the correct web.config file.
If not, then there is probably some other rule targeting the path you are trying to target with a stopProcessing="true" tag (like the one in the rule you posted here).
I'm trying to use the Slim PHP framework with IIS7. Now on some routes I keep getting a 404 from IIS which I find really confusing. Here's my index php:
require 'slim/slim.php';
\Slim\Slim::registerAutoloader();
$app = new \Slim\Slim();
$app->notFound(function () use ($app) {
echo("not found!");
});
$app->get("/books/:id", function($id){
echo("hello book " . $id . "!");
});
$app->get("/test",function(){
echo("testing");
});
$app->run();
On IIS (running PHP 5.3) I've setup the url rewritting to send all requests to my index.php file and disabled directory browsing. This seems to work fine as going to localhost/books/123 produces "hello book 123!". But when I go to localhost/test I just get a 404 error from IIS! If add a trailing slash to that url my slim notFound handler is triggered instead of my route handler.
If i create a directory called "test" it stops the 404 response but triggers the slim notFound handler rather than the defined route handler as I would expect. This seems really weird as I've disabled directory browsing.
I know my slim notFound handler is working ok as trying localhost/abc/xyz triggers the handler and works as expected.
Could anybody explain what is going on and why? Have I overlooked some configuration?
Thanks.
It turns out this weird behaviour was caused by my url rewrite rule on IIS. Doh!
I had the regex rule /.* rewrite to my index.php file rather than use .* as the regex.
The first slash wasn't being included as part of the rewritten url which then caused the issue I described. Changing the regex to just be .* fixed everything.
If anyone else encounters an issue like this then double check your url rewrite rule even if it seems to be working ok!
My very simple web.config file is:
<configuration>
<system.webServer>
<rewrite>
<rules>
<rule name="slim catch all" enabled="true">
<match url=".*" />
<action type="Rewrite" url="/index.php" />
<conditions>
<add input="{URL}" pattern="/content/.*" negate="true" />
</conditions>
</rule>
</rules>
</rewrite>
</system.webServer>
Note: this is using URL Rewrite 2.0 on IIS
Index.php is the file which sets up all the Slim routing. The condition is stopping requests to the /content/ path from being routed through Slim - this makes it a good place to store things like images, css files and javascript as the responses should be faster as they are not processed by Slim.
I was writing up this question and in the process, it forced me to think a little harder and I answered it myself, though I still don't completely understand why it solved it.
I have an account on a shared host with 2 domains registered. I'm using the Asp.Net stack to run a few things like a blog and another site I am planning to kick off eventually. Both of my domains point to the root; the first is the original I used to signup, the second is a root domain pointer I added. Here is how I want it to behave:
Directory Structure:
Root (www.domain1.com)
Root --\ Blog (www.domain1.com/blog)
Root --\ Site2 (should be directed here if www.domain2.com)
Root --\ Site2 --\ Junk (www.domain2.com/junk)
Right now, if you type in www.domain1.com or www.domain1.com/blog, that behaves as expected and I am fine with that. For www.domain2.com, I have the rewrite rule configured like this(from the web.config):
<rule name="Domain2">
<match url="(.*)(/)?" ignoreCase="false" />
<conditions logicalGrouping="MatchAll">
<add input="{HTTP_HOST}" pattern="(www\.)?domain2\.com" ignoreCase="false" />
</conditions>
<action type="Rewrite" url="/site2/{R:1}" />
</rule>
That rule is supposed to match any path if the host is domain2.com, pick off the path to the requested resource and format it properly. So when somebody types www.domain2.com/junk/default.aspx, in IIS, this resolves to www.domain2.com/site2/junk/default.aspx without the user ever knowing. This is mostly working as advertised except when the user does not type a trailing slash in a subfolder. IE:
www.domain2.com (works)
www.domain2.com/ (works)
www.domain2.com/junk/ (works)
www.domain2.com/junk (doesn't work!) IIS 7 looses its brain here and formats it out like www.domain2.com/site2/junk because a 2nd request is automatically issued for the trailing slash and a 404 happens.
So, I updated the action to be:
<action type="Rewrite" url="/site2/{R:1}/" />
This seems to have resolved it, but why doesn't IIS 7 now spit out www.domain2.com/junk2/default.aspx/ ? How does it know not to append a trailing slash to a document extension?
www.domain2.com/junk does not work because you added slash in match, but actual url to match does not contain it. It just contains "junk".
Also you need to add:
<rule name="Domain2" stopProcessing="true">
so it does not evaluate other rules if match is found. I suspect that you may see that what confuses you, is other rules you have setup.