1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
|
.. _iis:
Microsoft IIS
#############
Bugzilla works with IIS as a normal CGI application. These instructions assume
that you are using Windows 7 Ultimate x64. Procedures for other versions are
probably similar.
Begin by starting Internet Information Services (IIS) Manager.
:guilabel:`Start` --> :guilabel:`Administrators Tools` -->
:guilabel:`Internet Information Services (IIS) Manager`. Or run the command:
:command:`inetmgr`
Create a New Application
========================
Expand your :guilabel:`Server` until the :guilabel:`Default Web Site` shows
its children.
Right-click :guilabel:`Default Web Site` and select
:guilabel:`Add Application` from the menu.
Unde :guilabel:`Alias`, enter the alias for the website. This is the path
below the domain where you want Bugzilla to appear.
Under :guilabel:`Physical Path`, enter the path to Bugzilla,
:file:`C:\\Bugzilla`.
When finished, click :guilabel:`OK`.
Configure the Default Document
==============================
Click on the Application that you just created. Double-click on
:guilabel:`Default Document`, and click :guilabel:`Add` underneath the
Actions menu.
Under :guilabel:`Name`, enter ``index.cgi``.
All other default documents can be removed for this application.
.. warning:: Do not delete the default document from the :guilabel:`Default Website`.
Add Handler Mappings
====================
Ensure that you are at the Default Website. Under :guilabel:`IIS`,
double-click :guilabel:`Handler Mappings`. Under :guilabel:`Actions`, click
:guilabel:`Add Script Map`. You need to do this twice.
For the first one, set the following values (replacing paths if necessary):
* :guilabel:`Request Path`: ``*.pl``
* :guilabel:`Executable`: ``C:\Perl\bin\perl.exe "%s% %s%``
* :guilabel:`Name`: ``Perl Script Map``
At the prompt select :guilabel:`No`.
.. note:: The ActiveState Perl installer may have already created an entry for
.pl files that is limited to ``GET,HEAD,POST``. If so, this mapping should
be removed, as Bugzilla's .pl files are not designed to be run via a web
server.
.. todo:: My `source <https://wiki.mozilla.org/Installing_under_IIS_7.5>`_ says
to add a mapping for .pl, but that's sort of contradicted by the note above
from a different source. Which is right?
For the second one, set the following values (replacing paths if necessary):
* :guilabel:`Request Path`: ``*.cgi``
* :guilabel:`Executable`: ``C:\Perl\bin\perl.exe "%s% %s%``
* :guilabel:`Name`: ``CGI Script Map``
At the prompt select :guilabel:`No`.
Bugzilla Application
====================
Ensure that you are at the Bugzilla Application. Under :guilabel:`IIS`,
double-click :guilabel:`Handler Mappings`. Under :guilabel:`Actions`, click
:guilabel:`Add Script Map`.
Set the following values (replacing paths if necessary):
* :guilabel:`Request Path`: ``*.cgi``
* :guilabel:`Executable`: ``C:\Perl\bin\perl.exe -x"C:\Bugzilla" -wT "%s" %s``
* :guilabel:`Name`: ``Bugzilla``
At the prompt select :guilabel:`No`.
.. todo:: The Executable lines in the three things above are weirdly
inconsistent. Is this intentional? My source is `this page <https://wiki.mozilla.org/Installing_under_IIS_7.5>`_.
.. todo:: `LpSolit <http://lpsolit.wordpress.com/2010/10/22/make-bugzilla-work-with-iis7-easy/>`_
suggests there's a step to do with authorizing CGI modules. Where does that fit?
Common Problems
===============
Bugzilla runs but it's not possible to log in
You've probably configured IIS to use ActiveState's ISAPI DLL -- in other
words you're using PerlEx, or the executable IIS is configured to use is
:file:`PerlS.dll` or :file:`Perl30.dll`.
Reconfigure IIS to use :file:`perl.exe`.
IIS returns HTTP 502 errors
You probably forgot the ``-T`` argument to :file:`perl` when configuring the
executable in IIS.
XMLRPC interface not working with IIS
This is a known issue. See :bug:`708252`.
|
