CGI - Revision history

Gweiss at 19:16, 23 July 2024

2024-07-23T19:16:58Z

← Older revision		Revision as of 15:16, 23 July 2024
Line 9:		Line 9:
	<code>mkdir -p /web/userpages/''username''/cgi-bin</code>		<code>mkdir -p /web/userpages/''username''/cgi-bin</code>

	<code>chmod 701 ~/~~www~~/cgi-bin</code>		<code>chmod 701 /web/userpages/''username''/cgi-bin</code>

	3. Place your CGI files in the ~/~~www~~/cgi-bin directory. Ensure that the filenames for CGI executables end in .cgi OR .pl, otherwise the server will NOT recognize them as CGI scripts.		3. Place your CGI files in the /web/userpages/''username''/cgi-bin directory. Ensure that the filenames for CGI executables end in .cgi OR .pl, otherwise the server will NOT recognize them as CGI scripts.

	4. CGI script are accessed as a standard HTML link: <nowiki>http://~~www~~.cs.umbc.edu/~username/cgi-bin/filename.cgi</nowiki>		4. CGI script are accessed as a standard HTML link: <nowiki>http://userpages.cs.umbc.edu/''username''/cgi-bin/filename.cgi</nowiki>

	5. IMPORTANT: CGI scripts run as your account permissions. Be careful since a badly written script could allow someone to access your account/data. Do not put arbitrary CGI code up if you don't know how it works. Follow the best security practices when you are writing your own CGI script. There are many good references on the web for CGI script security issues. If you use CGI scripts, it is highly recommend to research and become familiar with the issues regarding CGI.		5. IMPORTANT: CGI scripts run as your account permissions. Be careful since a badly written script could allow someone to access your account/data. Do not put arbitrary CGI code up if you don't know how it works. Follow the best security practices when you are writing your own CGI script. There are many good references on the web for CGI script security issues. If you use CGI scripts, it is highly recommend to research and become familiar with the issues regarding CGI.

Gweiss at 19:15, 23 July 2024

2024-07-23T19:15:35Z

← Older revision		Revision as of 15:15, 23 July 2024
Line 7:		Line 7:
	2. Create a cgi-bin directory to store your CGI scripts.		2. Create a cgi-bin directory to store your CGI scripts.

	<code>mkdir -p ~/~~www~~/cgi-bin</code>		<code>mkdir -p /web/userpages/''username''/cgi-bin</code>

	<code>chmod 701 ~/www/cgi-bin</code>		<code>chmod 701 ~/www/cgi-bin</code>

Gweiss at 20:13, 6 August 2019

2019-08-06T20:13:16Z

← Older revision		Revision as of 16:13, 6 August 2019
Line 3:		Line 3:
	1. [[SSH/SCP/SFTP\|Login]] to your CSEE account.		1. [[SSH/SCP/SFTP\|Login]] to your CSEE account.

	2. Set up ~~the~~ [[Web Introduction\|Personal Web Site]] if you have not done so already.		2. Set up your [[Web Introduction\|Personal Web Site]] if you have not done so already.

	2. Create a cgi-bin directory to store your CGI scripts.		2. Create a cgi-bin directory to store your CGI scripts.

Gweiss: /* Using CGI on CSEE Personal Web Pages */

2019-08-06T20:10:32Z

Using CGI on CSEE Personal Web Pages

← Older revision		Revision as of 16:10, 6 August 2019
Line 2:		Line 2:

	1. [[SSH/SCP/SFTP\|Login]] to your CSEE account.		1. [[SSH/SCP/SFTP\|Login]] to your CSEE account.

			2. Set up the [[Web Introduction\|Personal Web Site]] if you have not done so already.

	2. Create a cgi-bin directory to store your CGI scripts.		2. Create a cgi-bin directory to store your CGI scripts.

Gweiss: /* Using CGI on CSEE Personal Web Pages */

2019-08-06T20:08:37Z

Using CGI on CSEE Personal Web Pages

← Older revision		Revision as of 16:08, 6 August 2019
Line 1:		Line 1:
	==Using CGI on CSEE Personal Web Pages==		==Using CGI on CSEE Personal Web Pages==

	1. ~~Log into~~ your CSEE account		1. [[SSH/SCP/SFTP\|Login]] to your CSEE account.

	2. Create a cgi-bin directory to store your CGI scripts		2. Create a cgi-bin directory to store your CGI scripts.

	<code>mkdir -p ~/www/cgi-bin</code>		<code>mkdir -p ~/www/cgi-bin</code>

Gweiss at 20:54, 17 June 2015

2015-06-17T20:54:41Z

← Older revision		Revision as of 16:54, 17 June 2015
Line 7:		Line 7:
	<code>mkdir -p ~/www/cgi-bin</code>		<code>mkdir -p ~/www/cgi-bin</code>

	<code>chmod ~~755~~ ~/www/cgi-bin</code>		<code>chmod 701 ~/www/cgi-bin</code>

	3. Place your CGI files in the ~/www/cgi-bin directory. Ensure that the filenames for CGI executables end in .cgi OR .pl, otherwise the server will NOT recognize them as CGI scripts.		3. Place your CGI files in the ~/www/cgi-bin directory. Ensure that the filenames for CGI executables end in .cgi OR .pl, otherwise the server will NOT recognize them as CGI scripts.

Gweiss: /* Using CGI on CSEE Personal Web Pages */

2007-08-27T04:10:30Z

Using CGI on CSEE Personal Web Pages

← Older revision		Revision as of 00:10, 27 August 2007
Line 13:		Line 13:
	4. CGI script are accessed as a standard HTML link: <nowiki>http://www.cs.umbc.edu/~username/cgi-bin/filename.cgi</nowiki>		4. CGI script are accessed as a standard HTML link: <nowiki>http://www.cs.umbc.edu/~username/cgi-bin/filename.cgi</nowiki>

	5. IMPORTANT: CGI scripts run as your account permissions. Be careful since a badly written script could allow someone to access your account/data. Do not put arbitrary CGI code up if you don't know how it works. Follow the best ~~seciroty~~ practices when you are writing your own CGI script. There are many good references on the web for CGI script security issues. If you use CGI scripts, it is highly recommend ~~you~~ become familiar with the issues regarding CGI.		5. IMPORTANT: CGI scripts run as your account permissions. Be careful since a badly written script could allow someone to access your account/data. Do not put arbitrary CGI code up if you don't know how it works. Follow the best security practices when you are writing your own CGI script. There are many good references on the web for CGI script security issues. If you use CGI scripts, it is highly recommend to research and become familiar with the issues regarding CGI.

	6. The PHP language can be used for writing CGI scripts. Read the documentation at [http://www.php.net/ PHP.net] and the [[PHP\|CSEE PHP Guide]] for more information.		6. The PHP language can be used for writing CGI scripts. Read the documentation at [http://www.php.net/ PHP.net] and the [[PHP\|CSEE PHP Guide]] for more information.

	7. CSEEIT reserves the right to discontinue access or disable user's CGI scripts that is doing something bad (such as, but not limited to enabling an email relay, providing illegal services, using too much CPU time, something that is deemed undesirable)~~. Keep in mind since this is state-owned equipment~~. Under Maryland ~~State~~ law, CSEEIT has the ~~authority to decide what is undesirable and~~ take appropriate action ~~as needed~~.		7. CSEEIT reserves the right to discontinue access or disable user's CGI scripts that is doing something bad (such as, but not limited to enabling an email relay, providing illegal services, using too much CPU time, or something that is deemed undesirable). Under Maryland state law, CSEEIT has the responsibility take appropriate action to protect the state-owned equipment in the CSEE department at UMBC.

Tevan1: /* Using CGI on CSEE Personal Web Pages */

2007-01-04T20:17:17Z

Using CGI on CSEE Personal Web Pages

← Older revision		Revision as of 16:17, 4 January 2007
Line 11:		Line 11:
	3. Place your CGI files in the ~/www/cgi-bin directory. Ensure that the filenames for CGI executables end in .cgi OR .pl, otherwise the server will NOT recognize them as CGI scripts.		3. Place your CGI files in the ~/www/cgi-bin directory. Ensure that the filenames for CGI executables end in .cgi OR .pl, otherwise the server will NOT recognize them as CGI scripts.

	4. CGI script are accessed as a standard HTML link: http://www.cs.umbc.edu/~username/cgi-bin/filename.cgi		4. CGI script are accessed as a standard HTML link: <nowiki>http://www.cs.umbc.edu/~username/cgi-bin/filename.cgi</nowiki>

	5. IMPORTANT: CGI scripts run as your account permissions. Be careful since a badly written script could allow someone to access your account/data. Do not put arbitrary CGI code up if you don't know how it works. Follow the best seciroty practices when you are writing your own CGI script. There are many good references on the web for CGI script security issues. If you use CGI scripts, it is highly recommend you become familiar with the issues regarding CGI.		5. IMPORTANT: CGI scripts run as your account permissions. Be careful since a badly written script could allow someone to access your account/data. Do not put arbitrary CGI code up if you don't know how it works. Follow the best seciroty practices when you are writing your own CGI script. There are many good references on the web for CGI script security issues. If you use CGI scripts, it is highly recommend you become familiar with the issues regarding CGI.

Tevan1: imported CGI guide to wiki format

2007-01-04T20:07:21Z

imported CGI guide to wiki format

New page

==Using CGI on CSEE Personal Web Pages==

1. Log into your CSEE account

2. Create a cgi-bin directory to store your CGI scripts

<code>mkdir -p ~/www/cgi-bin</code>

<code>chmod 755 ~/www/cgi-bin</code>

3. Place your CGI files in the ~/www/cgi-bin directory. Ensure that the filenames for CGI executables end in .cgi OR .pl, otherwise the server will NOT recognize them as CGI scripts.

4. CGI script are accessed as a standard HTML link: http://www.cs.umbc.edu/~username/cgi-bin/filename.cgi

5. IMPORTANT: CGI scripts run as your account permissions. Be careful since a badly written script could allow someone to access your account/data. Do not put arbitrary CGI code up if you don't know how it works. Follow the best seciroty practices when you are writing your own CGI script. There are many good references on the web for CGI script security issues. If you use CGI scripts, it is highly recommend you become familiar with the issues regarding CGI.

6. The PHP language can be used for writing CGI scripts. Read the documentation at [http://www.php.net/ PHP.net] and the [[PHP|CSEE PHP Guide]] for more information.

7. CSEEIT reserves the right to discontinue access or disable user's CGI scripts that is doing something bad (such as, but not limited to enabling an email relay, providing illegal services, using too much CPU time, something that is deemed undesirable). Keep in mind since this is state-owned equipment. Under Maryland State law, CSEEIT has the authority to decide what is undesirable and take appropriate action as needed.