IIS - Revision history

HobbesPDX at 22:20, 5 April 2012

2012-04-05T22:20:39Z

← Older revision		Revision as of 22:20, 5 April 2012
Line 3:		Line 3:
	PHP can run on IIS, so a Joomla! web site also can run on IIS.		PHP can run on IIS, so a Joomla! web site also can run on IIS.

	The PHP.net website should be referenced, regarding the installation of PHP on Windows and the ~~configuraiton~~ of IIS to process PHP webpages and scripts.		The PHP.net website should be referenced, regarding the installation of PHP on Windows and the configuration of IIS to process PHP webpages and scripts.

	To get started, here are some helpful links for developers who want to install PHP and Joomla! on IIS.		To get started, here are some helpful links for developers who want to install PHP and Joomla! on IIS.
Line 20:		Line 20:

	Windows servers have a user called <code>IUSR</code>, which corresponds to the <code>apache</code> user on many Linux systems. PHP scripts run under the IUSR account.		Windows servers have a user called <code>IUSR</code>, which corresponds to the <code>apache</code> user on many Linux systems. PHP scripts run under the IUSR account.
			(For IIS 7.5, this may be the group WEB\Users)

	====Levels====		====Levels====

Beanluc: Move section - it was inserted in the middle of explu

2011-08-08T03:13:19Z

Move section - it was inserted in the middle of explu

@@ Line 51: / Line 51: @@
 Run the Joomla installer again, and enjoy your PHP user's write privileges in your website folder.
 ==[[Restricting access to the backend by IP address]]==
@@ Line 73: / Line 90: @@
 [[http://www.iis.net/ConfigReference/system.webServer/security/ipSecurity]]
 (thanks to Sam Moffat for above info)
 <noinclude>[[Category:IIS]][[Category:FAQ]]</noinclude>

Jzlcdh: /* Restricting access to the backend by IP address */

2011-07-13T12:58:22Z

Restricting access to the backend by IP address

← Older revision		Revision as of 12:58, 13 July 2011
Line 59:		Line 59:
	"Roles" and then "Web Server (IIS). From here select "Add Role Services" and		"Roles" and then "Web Server (IIS). From here select "Add Role Services" and
	in the window that pops up, scroll down to security and select the "IP And		in the window that pops up, scroll down to security and select the "IP And
	Domain Security Option" (see screenshot below) and then hit next to install.		Domain Security Option" (see screenshot below)
			[[File:IPrestrictionIIS.jpg]]
			and then hit next to install.
	Once you've got it installed, open up the IIS Manager MMC panel (if you have		Once you've got it installed, open up the IIS Manager MMC panel (if you have
	it open already, you will need to restart it for the appropriate panel to		it open already, you will need to restart it for the appropriate panel to

Jzlcdh: Added: Restricting access to the backend by IP address

2011-07-13T12:53:45Z

Added: Restricting access to the backend by IP address

← Older revision		Revision as of 12:53, 13 July 2011
Line 51:		Line 51:

	Run the Joomla installer again, and enjoy your PHP user's write privileges in your website folder.		Run the Joomla installer again, and enjoy your PHP user's write privileges in your website folder.

			==[[Restricting access to the backend by IP address]]==

			You can utilise server based IP protection.
			If you're running IIS 7.5 on Windows Server 2008, you can use the IP and
			Domain Security option. Go to the Server Manager MMC panel and select
			"Roles" and then "Web Server (IIS). From here select "Add Role Services" and
			in the window that pops up, scroll down to security and select the "IP And
			Domain Security Option" (see screenshot below) and then hit next to install.
			Once you've got it installed, open up the IIS Manager MMC panel (if you have
			it open already, you will need to restart it for the appropriate panel to
			appear; this also means the server manager one might not be useful to you)
			and navigate down to the administrator directory of the site. Click on the
			"IPv4 Address and Domain Restrictions". You can change the default behaviour
			by clicking "Edit Feature Settings" and setting the default value for
			unspecified clients to deny. Then add allow entries for your trusted IP
			addresses or subnets.
			Check out the following article for details as well:
			[[http://www.iis.net/ConfigReference/system.webServer/security/ipSecurity]]
			(thanks to Sam Moffat for above info)

	==[[Search Engine Friendly URLs]]==		==[[Search Engine Friendly URLs]]==

Mvangeest: Adjusted link after page move

2011-06-09T15:11:55Z

Adjusted link after page move

← Older revision		Revision as of 15:11, 9 June 2011
Line 52:		Line 52:
	Run the Joomla installer again, and enjoy your PHP user's write privileges in your website folder.		Run the Joomla installer again, and enjoy your PHP user's write privileges in your website folder.

	==[[~~SEF URLs on IIS\|SEF~~ URLs]]==		==[[Search Engine Friendly URLs]]==
	The functioning of SEF URLs depends on "URL rewriting" - matching patterns in incoming HTTP requests, and passing the request to the webserver in a different format. Joomla can only understand the parameters present in the "ugly" request, so the human-readable path in the incoming HTTP request needs to be re-written for Joomla.		The functioning of SEF URLs depends on "URL rewriting" - matching patterns in incoming HTTP requests, and passing the request to the webserver in a different format. Joomla can only understand the parameters present in the "ugly" request, so the human-readable path in the incoming HTTP request needs to be re-written for Joomla.

Line 67:		Line 67:
	The IIS7 module configures and stores its rules in a very different way than the format Apache provides via .htaccess. The rules are stored as XML data in the web.config file in a website's root. The IIS Management Console provides a GUI and wizard for creating and testing rules. The wizard is capable of reading a text file with .htaccess-type rules and converting them to the native format.		The IIS7 module configures and stores its rules in a very different way than the format Apache provides via .htaccess. The rules are stored as XML data in the web.config file in a website's root. The IIS Management Console provides a GUI and wizard for creating and testing rules. The wizard is capable of reading a text file with .htaccess-type rules and converting them to the native format.

	~~Specific '''instruction information''' is available on '''~~[[SEF URLs on IIS]]~~'''~~.		See [[Enabling Search Engine Friendly (SEF) URLs on IIS]] for instructions.

	<noinclude>[[Category:IIS]][[Category:FAQ]]</noinclude>		<noinclude>[[Category:IIS]][[Category:FAQ]]</noinclude>

Mvangeest: moved IIS and Joomla to IIS: Moved page to create landing page

2011-06-09T11:50:46Z

moved IIS and Joomla to IIS: Moved page to create landing page

← Older revision	Revision as of 11:50, 9 June 2011
(No difference)

Mvangeest: Merging from IIS

2011-06-09T11:49:10Z

Merging from IIS

← Older revision		Revision as of 11:49, 9 June 2011
Line 1:		Line 1:
	Whilst IIS accounts for relatively few users, compared to Apache, there are enough to warrant providing information which is unique.		Whilst IIS (Internet Information Services, a Microsoft web server) accounts for relatively few users, compared to Apache, there are enough to warrant providing information which is unique.

	PHP can run on IIS ~~(Microsoft web server, Internet Information Services). So~~, a Joomla! web site also can run on IIS.		PHP can run on IIS, so a Joomla! web site also can run on IIS.

	The PHP.net website should be referenced, regarding the installation of PHP on Windows and the configuraiton of IIS to process PHP webpages and scripts.		The PHP.net website should be referenced, regarding the installation of PHP on Windows and the configuraiton of IIS to process PHP webpages and scripts.

			To get started, here are some helpful links for developers who want to install PHP and Joomla! on IIS.

			* Install Joomla for Windows and IIS using the Web Platform Installer - http://www.microsoft.com/web/joomla
			* PHP on Windows and IIS; building an IIS-optimized PHP - http://www.microsoft.com/web/php

	The two most common problems encountered by Joomla! admins whose sites are on IIS webservers are:		The two most common problems encountered by Joomla! admins whose sites are on IIS webservers are:

Mvangeest: Adjusted links

2011-05-20T12:32:30Z

Adjusted links

← Older revision		Revision as of 12:32, 20 May 2011
Line 47:		Line 47:
	Run the Joomla installer again, and enjoy your PHP user's write privileges in your website folder.		Run the Joomla installer again, and enjoy your PHP user's write privileges in your website folder.

	==SEF URLs==		==[[SEF URLs on IIS\|SEF URLs]]==
	The functioning of SEF URLs depends on "URL rewriting" - matching patterns in incoming HTTP requests, and passing the request to the webserver in a different format. Joomla can only understand the parameters present in the "ugly" request, so the human-readable path in the incoming HTTP request needs to be re-written for Joomla.		The functioning of SEF URLs depends on "URL rewriting" - matching patterns in incoming HTTP requests, and passing the request to the webserver in a different format. Joomla can only understand the parameters present in the "ugly" request, so the human-readable path in the incoming HTTP request needs to be re-written for Joomla.

Line 62:		Line 62:
	The IIS7 module configures and stores its rules in a very different way than the format Apache provides via .htaccess. The rules are stored as XML data in the web.config file in a website's root. The IIS Management Console provides a GUI and wizard for creating and testing rules. The wizard is capable of reading a text file with .htaccess-type rules and converting them to the native format.		The IIS7 module configures and stores its rules in a very different way than the format Apache provides via .htaccess. The rules are stored as XML data in the web.config file in a website's root. The IIS Management Console provides a GUI and wizard for creating and testing rules. The wizard is capable of reading a text file with .htaccess-type rules and converting them to the native format.

	Specific '''instruction information''' is available ~~about~~ '''[[~~SEO and~~ IIS]]'''.		Specific '''instruction information''' is available on '''[[SEF URLs on IIS]]'''.

	<noinclude>[[Category:IIS]][[Category:FAQ]]</noinclude>		<noinclude>[[Category:IIS]][[Category:FAQ]]</noinclude>

G1smd: Reworded to show the correct direction of travel for a rewrite. It's a URL to filepath translation!

2011-04-24T15:44:18Z

Reworded to show the correct direction of travel for a rewrite. It's a URL to filepath translation!

← Older revision		Revision as of 15:44, 24 April 2011
Line 48:		Line 48:

	==SEF URLs==		==SEF URLs==
	The functioning of SEF URLs depends on "URL rewriting" - matching patterns in incoming HTTP requests, and passing the request to the webserver in a different format. Joomla can only understand the parameters present in the "ugly" ~~URL~~, so the human-readable path in the incoming HTTP request needs to be re-written for Joomla.		The functioning of SEF URLs depends on "URL rewriting" - matching patterns in incoming HTTP requests, and passing the request to the webserver in a different format. Joomla can only understand the parameters present in the "ugly" request, so the human-readable path in the incoming HTTP request needs to be re-written for Joomla.

	===Apache's mod_rewrite===		===Apache's mod_rewrite===
	<code>mod_rewrite</code> is the familiar way by which many webmasters ~~turn~~ "ugly" ~~URL paths~~ like <code>/index.php?option=com_content&view=article&id=999&Itemid=23</code> ~~into nice human-readable, spider-friendly ones like <code>/about_us/contact_information</code>~~. A text file called .htaccess contains the rules, which are ~~writen~~ according to a ~~familiar (to many)~~ syntax.		<code>mod_rewrite</code> is the familiar way by which many webmasters translate nice human-readable, spider-friendly URL requests like <code>/about_us/contact_information</code> into the "ugly" internal server path like <code>/index.php?option=com_content&view=article&id=999&Itemid=23</code> that makes Joomla serve up some content. A text file called .htaccess contains the rewrite rules, which are written according to a specific syntax.

	===IIS===		===IIS===

Chris Davenport: Added categorisation.

2010-03-17T19:10:46Z

Added categorisation.

← Older revision		Revision as of 19:10, 17 March 2010
Line 64:		Line 64:
	Specific '''instruction information''' is available about '''[[SEO and IIS]]'''.		Specific '''instruction information''' is available about '''[[SEO and IIS]]'''.

	[[Category:FAQ]]		<noinclude>[[Category:IIS]][[Category:FAQ]]</noinclude>