Fossil SCM

Assorted small tweaks to www/server/windows/iis.md

wyoung 2019-08-19 10:22 server-docs

Commit b5fefeec237395976cda6b888c982bbb322b2ea0afd4df4f02bbfa2e8900d42e

Parent 3995a3c7ae8f362…

1 file changed +13 -11

M www/server/windows/iis.md

+13 -11

		--- www/server/windows/iis.md
		+++ www/server/windows/iis.md
		@@ -45,18 +45,15 @@
45	45	system boot, before anyone has logged in interactively.
46	46
47	47
48	48	## <a name="install"></a>Install IIS
49	49
50		-IIS might not already be already in your system, so follow the path
	50	+IIS might not be installed in your system yet, so follow the path
51	51	appropriate to your host OS. We’ve tested only the latest Microsoft
52	52	OSes as of the time of this writing, but the basic process should be
53	53	similar on older OSes.
54	54
55		-The default set of IIS features there will suffice for this tutorial,
56		-but you might want to enable additional features.
57		-
58	55
59	56	### Windows Server 2019
60	57
61	58	1. Start “Server Manager”
62	59	2. Tell it you want to “Add roles and features”
		@@ -70,12 +67,15 @@
70	67	2. Go to “Programs”
71	68	3. Select “Turn Windows features on or off” in the left-side pane
72	69	4. In the “Windows Features” dialog, enable “Internet Information
73	70	Services”
74	71
	72	+The default set of IIS features there will suffice for this tutorial,
	73	+but you might want to enable additional features.
	74	+
75	75
76		-## Reverse Proxy with URL Rewriting
	76	+## Setting up the Proxy
77	77
78	78	The stock IIS setup doesn’t have reverse proxying features, but they’re
79	79	easily added through extensions. You will need to install the
80	80	[Application Request Routing][arr] and [URL Rewrite][ure] extensions. In
81	81	my testing here, URL Rewrite showed up immediately after installing it,
		@@ -83,11 +83,11 @@
83	83
84	84	You can install these things through the direct links above, or you can
85	85	do it via the Web Platform Installer feature of IIS Manager (a.k.a.
86	86	`INETMGR`).
87	87
88		-Now you can set these extensions up in IIS Manager:
	88	+Set these extensions up in IIS Manager like so:
89	89
90	90	1. Double-click the “Application Request Routing Cache” icon.
91	91
92	92	2. Right-click in the window that results, and select “Server Proxy
93	93	Settings...”
		@@ -97,31 +97,33 @@
97	97
98	98	4. Return to the top server-level configuration area of IIS Manager and
99	99	double-click the “URL Rewrite” icon. Alternately, you might find
100	100	“URL Rewrite” in the right-side pane from within the ARR settings.
101	101
102		-5. Right click in the window that results and click “Add Rule(s)...”
	102	+5. Right click in the window that results, and click “Add Rule(s)...”
103	103	Tell it you want a “Blank rule” under “Inbound rules”.
104	104
105	105	6. In the dialog that results, create a new rule called “Fossil repo
106	106	proxy.” Set the “Pattern” to “`^(.*)$`” and “Rewrite URL” set to
107	107	“`http://localhost:9000/{R:1}`”. That tells it to take everything in
108	108	the path part of the URL and send it down to localhost:9000, where
109	109	`fossil server` is listening.
110	110
111	111	7. Click “Apply” in the right-side pane, then get back to the top level
112		- configuration for the server and click “Restart” in that same pane.
	112	+ configuration for the server, and click “Restart” in that same pane.
113	113
114	114	At this point, if you go to `http://localhost/` in your browser, you
115	115	should see your Fossil repository’s web interface instead of the default
116	116	IIS web site, as before you did all of the above.
117	117
118	118	This is a very simple configuration. You can do more complicated and
119	119	interesting things with this, such as redirecting only `/code` URLs to
120		-Fossil by setting the Pattern in step 6 to “`^/code(.*)$`”. IIS would
121		-then directly serve all other URLs. You could also intermix ASP.NET
122		-applications in the URL scheme in this way.
	120	+Fossil by setting the Pattern in step 6 to “`^/code(.*)$`”. (You would
	121	+also need to pass `--baseurl http://example.com/code` in the `fossil
	122	+server` command to make this work properly.) IIS would then directly
	123	+serve all other URLs. You could also intermix ASP.NET applications in
	124	+the URL scheme in this way.
123	125
124	126	See the documentation on [URL Rewrite rules][urr] for more ideas.
125	127
126	128	[Return to the top-level Fossil server article.](../)
127	129
128	130

	--- www/server/windows/iis.md
	+++ www/server/windows/iis.md
	@@ -45,18 +45,15 @@
45	system boot, before anyone has logged in interactively.
46
47
48	## <a name="install"></a>Install IIS
49
50	IIS might not already be already in your system, so follow the path
51	appropriate to your host OS. We’ve tested only the latest Microsoft
52	OSes as of the time of this writing, but the basic process should be
53	similar on older OSes.
54
55	The default set of IIS features there will suffice for this tutorial,
56	but you might want to enable additional features.
57
58
59	### Windows Server 2019
60
61	1. Start “Server Manager”
62	2. Tell it you want to “Add roles and features”
	@@ -70,12 +67,15 @@
70	2. Go to “Programs”
71	3. Select “Turn Windows features on or off” in the left-side pane
72	4. In the “Windows Features” dialog, enable “Internet Information
73	Services”
74



75
76	## Reverse Proxy with URL Rewriting
77
78	The stock IIS setup doesn’t have reverse proxying features, but they’re
79	easily added through extensions. You will need to install the
80	[Application Request Routing][arr] and [URL Rewrite][ure] extensions. In
81	my testing here, URL Rewrite showed up immediately after installing it,
	@@ -83,11 +83,11 @@
83
84	You can install these things through the direct links above, or you can
85	do it via the Web Platform Installer feature of IIS Manager (a.k.a.
86	`INETMGR`).
87
88	Now you can set these extensions up in IIS Manager:
89
90	1. Double-click the “Application Request Routing Cache” icon.
91
92	2. Right-click in the window that results, and select “Server Proxy
93	Settings...”
	@@ -97,31 +97,33 @@
97
98	4. Return to the top server-level configuration area of IIS Manager and
99	double-click the “URL Rewrite” icon. Alternately, you might find
100	“URL Rewrite” in the right-side pane from within the ARR settings.
101
102	5. Right click in the window that results and click “Add Rule(s)...”
103	Tell it you want a “Blank rule” under “Inbound rules”.
104
105	6. In the dialog that results, create a new rule called “Fossil repo
106	proxy.” Set the “Pattern” to “`^(.*)$`” and “Rewrite URL” set to
107	“`http://localhost:9000/{R:1}`”. That tells it to take everything in
108	the path part of the URL and send it down to localhost:9000, where
109	`fossil server` is listening.
110
111	7. Click “Apply” in the right-side pane, then get back to the top level
112	configuration for the server and click “Restart” in that same pane.
113
114	At this point, if you go to `http://localhost/` in your browser, you
115	should see your Fossil repository’s web interface instead of the default
116	IIS web site, as before you did all of the above.
117
118	This is a very simple configuration. You can do more complicated and
119	interesting things with this, such as redirecting only `/code` URLs to
120	Fossil by setting the Pattern in step 6 to “`^/code(.*)$`”. IIS would
121	then directly serve all other URLs. You could also intermix ASP.NET
122	applications in the URL scheme in this way.


123
124	See the documentation on [URL Rewrite rules][urr] for more ideas.
125
126	[Return to the top-level Fossil server article.](../)
127
128

	--- www/server/windows/iis.md
	+++ www/server/windows/iis.md
	@@ -45,18 +45,15 @@
45	system boot, before anyone has logged in interactively.
46
47
48	## <a name="install"></a>Install IIS
49
50	IIS might not be installed in your system yet, so follow the path
51	appropriate to your host OS. We’ve tested only the latest Microsoft
52	OSes as of the time of this writing, but the basic process should be
53	similar on older OSes.
54



55
56	### Windows Server 2019
57
58	1. Start “Server Manager”
59	2. Tell it you want to “Add roles and features”
	@@ -70,12 +67,15 @@
67	2. Go to “Programs”
68	3. Select “Turn Windows features on or off” in the left-side pane
69	4. In the “Windows Features” dialog, enable “Internet Information
70	Services”
71
72	The default set of IIS features there will suffice for this tutorial,
73	but you might want to enable additional features.
74
75
76	## Setting up the Proxy
77
78	The stock IIS setup doesn’t have reverse proxying features, but they’re
79	easily added through extensions. You will need to install the
80	[Application Request Routing][arr] and [URL Rewrite][ure] extensions. In
81	my testing here, URL Rewrite showed up immediately after installing it,
	@@ -83,11 +83,11 @@
83
84	You can install these things through the direct links above, or you can
85	do it via the Web Platform Installer feature of IIS Manager (a.k.a.
86	`INETMGR`).
87
88	Set these extensions up in IIS Manager like so:
89
90	1. Double-click the “Application Request Routing Cache” icon.
91
92	2. Right-click in the window that results, and select “Server Proxy
93	Settings...”
	@@ -97,31 +97,33 @@
97
98	4. Return to the top server-level configuration area of IIS Manager and
99	double-click the “URL Rewrite” icon. Alternately, you might find
100	“URL Rewrite” in the right-side pane from within the ARR settings.
101
102	5. Right click in the window that results, and click “Add Rule(s)...”
103	Tell it you want a “Blank rule” under “Inbound rules”.
104
105	6. In the dialog that results, create a new rule called “Fossil repo
106	proxy.” Set the “Pattern” to “`^(.*)$`” and “Rewrite URL” set to
107	“`http://localhost:9000/{R:1}`”. That tells it to take everything in
108	the path part of the URL and send it down to localhost:9000, where
109	`fossil server` is listening.
110
111	7. Click “Apply” in the right-side pane, then get back to the top level
112	configuration for the server, and click “Restart” in that same pane.
113
114	At this point, if you go to `http://localhost/` in your browser, you
115	should see your Fossil repository’s web interface instead of the default
116	IIS web site, as before you did all of the above.
117
118	This is a very simple configuration. You can do more complicated and
119	interesting things with this, such as redirecting only `/code` URLs to
120	Fossil by setting the Pattern in step 6 to “`^/code(.*)$`”. (You would
121	also need to pass `--baseurl http://example.com/code` in the `fossil
122	server` command to make this work properly.) IIS would then directly
123	serve all other URLs. You could also intermix ASP.NET applications in
124	the URL scheme in this way.
125
126	See the documentation on [URL Rewrite rules][urr] for more ideas.
127
128	[Return to the top-level Fossil server article.](../)
129
130

Fossil SCM

Keyboard Shortcuts