IBM HTTP-Server for AS/400 Configuration - Revision history

PoC: Links

2026-03-01T01:31:23Z

Links

← Older revision		Revision as of 03:31, 1 March 2026
Line 27:		Line 27:
	== Complete configuration documentation ==		== Complete configuration documentation ==
	# Template Configuration - Examples for all possible directives		# Template Configuration - Examples for all possible directives
	# https://www-01.ibm.com/software/webservers/httpservers/doc/v4r4/wmg/RZAG2M07.HTM		# <nowiki>https://www-01.ibm.com/software/webservers/httpservers/doc/v4r4/wmg/RZAG2M07.HTM</nowiki>
	# (Page no longer existing)		# (Page no longer existing)
	#------------------------------------------------------------------------------		#------------------------------------------------------------------------------
Line 8,349:		Line 8,349:
	== Weblinks ==		== Weblinks ==
	* [https://www.ibm.com/resources/publications/OutputPubsDetails?PubID=GC41543405 HTTP Server for AS/400 Webmaster's Guide], GC41-5434-05		* [https://www.ibm.com/resources/publications/OutputPubsDetails?PubID=GC41543405 HTTP Server for AS/400 Webmaster's Guide], GC41-5434-05
			**[https://web.archive.org/web/20160216215938/https://www-01.ibm.com/software/webservers/httpservers/doc/v4r4/wmg/RZAG2M07.HTMHTTP Server for AS/400 Webmaster's Guide: Using server directives in a configuration file], archive.org
	* [http://www.redbooks.ibm.com/redbooks/pdfs/sg245645.pdf AS/400 HTTP Server Performance and Capacity Planning], IBM RedBook SG24-5645-00		* [http://www.redbooks.ibm.com/redbooks/pdfs/sg245645.pdf AS/400 HTTP Server Performance and Capacity Planning], IBM RedBook SG24-5645-00
	* [https://www.ibm.com/resources/publications/OutputPubsDetails?PubID=sg24481501 Cool Title About the AS/400 and Internet], SG24-4815-01.		* [https://www.ibm.com/resources/publications/OutputPubsDetails?PubID=sg24481501 Cool Title About the AS/400 and Internet], SG24-4815-01.

PoC: /* Links */ Rename section

2026-01-04T15:37:47Z

Links: Rename section

← Older revision		Revision as of 17:37, 4 January 2026
Line 8,347:		Line 8,347:
	Why would one serve HTML pages from the apparently cumbersome <code>QSYS.LIB</code> filesystem? I have not gathered measurements yet, but I'd expect better performance. It's well known that even the IFS isn't exactly a speed wonder. On older and slower machines, this can truly make a difference.		Why would one serve HTML pages from the apparently cumbersome <code>QSYS.LIB</code> filesystem? I have not gathered measurements yet, but I'd expect better performance. It's well known that even the IFS isn't exactly a speed wonder. On older and slower machines, this can truly make a difference.

	== ~~Links~~ ==		== Weblinks ==
	* [https://www.ibm.com/resources/publications/OutputPubsDetails?PubID=GC41543405 HTTP Server for AS/400 Webmaster's Guide], GC41-5434-05		* [https://www.ibm.com/resources/publications/OutputPubsDetails?PubID=GC41543405 HTTP Server for AS/400 Webmaster's Guide], GC41-5434-05
	* [http://www.redbooks.ibm.com/redbooks/pdfs/sg245645.pdf AS/400 HTTP Server Performance and Capacity Planning], IBM RedBook SG24-5645-00		* [http://www.redbooks.ibm.com/redbooks/pdfs/sg245645.pdf AS/400 HTTP Server Performance and Capacity Planning], IBM RedBook SG24-5645-00

PoC: /* Links */ +link (for future expansion of the article)

2024-10-22T09:53:13Z

Links: +link (for future expansion of the article)

← Older revision		Revision as of 11:53, 22 October 2024
Line 8,351:		Line 8,351:
	* [http://www.redbooks.ibm.com/redbooks/pdfs/sg245645.pdf AS/400 HTTP Server Performance and Capacity Planning], IBM RedBook SG24-5645-00		* [http://www.redbooks.ibm.com/redbooks/pdfs/sg245645.pdf AS/400 HTTP Server Performance and Capacity Planning], IBM RedBook SG24-5645-00
	* [https://www.ibm.com/resources/publications/OutputPubsDetails?PubID=sg24481501 Cool Title About the AS/400 and Internet], SG24-4815-01.		* [https://www.ibm.com/resources/publications/OutputPubsDetails?PubID=sg24481501 Cool Title About the AS/400 and Internet], SG24-4815-01.
			* [https://www.ibm.com/docs/en/i/7.4?topic=programming-writing-persistent-cgi-programs Writing persistent CGI programs], IBM.com

	== Footnotes ==		== Footnotes ==

PoC: /* Using source physical files */ typo

2024-10-19T21:37:13Z

Using source physical files: typo

← Older revision		Revision as of 23:37, 19 October 2024
Line 8,341:		Line 8,341:
	* The member ''type'' '''must''' be <code>HTML</code>. Anything else will be sent with a MIME type of <code>text/plain</code>.		* The member ''type'' '''must''' be <code>HTML</code>. Anything else will be sent with a MIME type of <code>text/plain</code>.
	** This precludes using CSS files, because they will be delivered with the wrong MIME type. You can work around this by using ''server side includes'' with the <code>include virtual</code> HTML comment directive. You need to enable ''imbeds'' in the server configuration, though.		** This precludes using CSS files, because they will be delivered with the wrong MIME type. You can work around this by using ''server side includes'' with the <code>include virtual</code> HTML comment directive. You need to enable ''imbeds'' in the server configuration, though.
	*** The configuration states that ''files'' refer to IFS includes only, but <code>include virtual</code> works just fine with QSYS.LIB members. They need to be referred with a ''Pass'' directive, though.		*** The configuration documentation states that ''files'' refer to IFS includes only, but <code>include virtual</code> works just fine with QSYS.LIB members. They need to be referred with a ''Pass'' directive, though.

	If you prefer to edit members with SEU, SRC PFs should be created with <code>rcdlen(134)</code>, yielding a maximum line length of 122. No sideways scrolling is necessary with this setting on a 27×132 (emulated) terminal, while maintaining ample horizontal space for formatting purposes.		If you prefer to edit members with SEU, SRC PFs should be created with <code>rcdlen(134)</code>, yielding a maximum line length of 122. No sideways scrolling is necessary with this setting on a 27×132 (emulated) terminal, while maintaining ample horizontal space for formatting purposes.

PoC: /* Using source physical files */ More precise

2024-10-19T21:36:21Z

Using source physical files: More precise

← Older revision		Revision as of 23:36, 19 October 2024
Line 8,340:		Line 8,340:
	</syntaxhighlight>		</syntaxhighlight>
	* The member ''type'' '''must''' be <code>HTML</code>. Anything else will be sent with a MIME type of <code>text/plain</code>.		* The member ''type'' '''must''' be <code>HTML</code>. Anything else will be sent with a MIME type of <code>text/plain</code>.
	** This precludes using CSS files, because they will be delivered with the wrong MIME type. You can work around this by using ''server side includes'' with the <code>include virtual</code> directive.		** This precludes using CSS files, because they will be delivered with the wrong MIME type. You can work around this by using ''server side includes'' with the <code>include virtual</code> HTML comment directive. You need to enable ''imbeds'' in the server configuration, though.
			*** The configuration states that ''files'' refer to IFS includes only, but <code>include virtual</code> works just fine with QSYS.LIB members. They need to be referred with a ''Pass'' directive, though.

	If you prefer to edit members with SEU, SRC PFs should be created with <code>rcdlen(134)</code>, yielding a maximum line length of 122. No sideways scrolling is necessary with this setting on a 27×132 (emulated) terminal, while maintaining ample horizontal space for formatting purposes.		If you prefer to edit members with SEU, SRC PFs should be created with <code>rcdlen(134)</code>, yielding a maximum line length of 122. No sideways scrolling is necessary with this setting on a 27×132 (emulated) terminal, while maintaining ample horizontal space for formatting purposes.

PoC: /* Minimal working configuration examples */ Removed lines

2024-10-19T21:28:00Z

Minimal working configuration examples: Removed lines

← Older revision		Revision as of 23:28, 19 October 2024
Line 8,268:		Line 8,268:
	Each standard (aka, non-admin) site has one member with the same name in both of <code>QATMHINSTC</code> and <code>QATMHTTPC</code>. The former establishes parameters for the server instance, the latter ist the configuration itself.		Each standard (aka, non-admin) site has one member with the same name in both of <code>QATMHINSTC</code> and <code>QATMHTTPC</code>. The former establishes parameters for the server instance, the latter ist the configuration itself.

	<syntaxhighlight lang="Bash" ~~line~~>		<syntaxhighlight lang="Bash">
	# Specify the port on which you want the server to listen for requests		# Specify the port on which you want the server to listen for requests
	Port 8080		Port 8080
Line 8,312:		Line 8,312:

	=== Webroot in the IFS ===		=== Webroot in the IFS ===
	<syntaxhighlight lang="Bash" ~~line~~>		<syntaxhighlight lang="Bash">
	# Set up access control for the server		# Set up access control for the server
	Pass /* /QOpenSys/var/www/mysite/*		Pass /* /QOpenSys/var/www/mysite/*

PoC: /* Using source physical files */ Exanded

2024-10-19T21:27:12Z

Using source physical files: Exanded

← Older revision		Revision as of 23:27, 19 October 2024
Line 8,326:		Line 8,326:
	=== Using source physical files ===		=== Using source physical files ===
	You can also serve web pages from source physical files. Each member is a separate HTML document. Because the naming scheme is predefined by OS/400 a lot of page-individual configuration needs to be done:		You can also serve web pages from source physical files. Each member is a separate HTML document. Because the naming scheme is predefined by OS/400 a lot of page-individual configuration needs to be done:
	<syntaxhighlight lang="Bash" ~~line~~>		<syntaxhighlight lang="Bash">
	# Pages via QSYS.LIB		# Pages via QSYS.LIB
	Pass /index.html /QSYS.LIB/QGPL.LIB/MYSITE.FILE/INDEX.MBR		Pass /index.html /QSYS.LIB/QGPL.LIB/MYSITE.FILE/INDEX.MBR
Line 8,336:		Line 8,336:
	* The free formatting capability of HTML source often yields some very long lines along many short ones. Since the <code>QSYS.LIB</code> is hosting record-oriented files exclusively, this might result in considerable overhead of allocated storage, and probably more data to be read from disk.		* The free formatting capability of HTML source often yields some very long lines along many short ones. Since the <code>QSYS.LIB</code> is hosting record-oriented files exclusively, this might result in considerable overhead of allocated storage, and probably more data to be read from disk.
	* You can't meaningfully store binary streams (images) in source PFs. One way to deal with this is to ''imbed'' a Base64 encoded copy in the HTML <code><nowiki><img src></nowiki></code> tag. The Base64 decoding ignores line wrapping, so you can fill up lines to the maximum configured length. Example:		* You can't meaningfully store binary streams (images) in source PFs. One way to deal with this is to ''imbed'' a Base64 encoded copy in the HTML <code><nowiki><img src></nowiki></code> tag. The Base64 decoding ignores line wrapping, so you can fill up lines to the maximum configured length. Example:
	<syntaxhighlight lang="html" ~~line~~>		<syntaxhighlight lang="html">
	<img src="data:image/jpeg;base64,base64-encoded-text-goes-here">		<img src="data:image/jpeg;base64,base64-encoded-text-goes-here">
	</syntaxhighlight>		</syntaxhighlight>
	* The member ''type'' '''must''' be <code>HTML</code>. Anything else will be sent with a MIME type of <code>text/plain</code>.		* The member ''type'' '''must''' be <code>HTML</code>. Anything else will be sent with a MIME type of <code>text/plain</code>.
			** This precludes using CSS files, because they will be delivered with the wrong MIME type. You can work around this by using ''server side includes'' with the <code>include virtual</code> directive.

	Why would one serve HTML pages from the apparently cumbersome <code>QSYS.LIB</code> filesystem? I have not gathered measurements yet, but I'd expect better performance. It's well known that even the IFS isn't exactly a ~~performance~~ wonder. On older and slower machines, this can truly make a difference.		If you prefer to edit members with SEU, SRC PFs should be created with <code>rcdlen(134)</code>, yielding a maximum line length of 122. No sideways scrolling is necessary with this setting on a 27×132 (emulated) terminal, while maintaining ample horizontal space for formatting purposes.

			Why would one serve HTML pages from the apparently cumbersome <code>QSYS.LIB</code> filesystem? I have not gathered measurements yet, but I'd expect better performance. It's well known that even the IFS isn't exactly a speed wonder. On older and slower machines, this can truly make a difference.

	== Links ==		== Links ==

PoC: /* Using source physical files */ code

2024-10-07T02:17:13Z

Using source physical files: code

← Older revision		Revision as of 04:17, 7 October 2024
Line 8,335:		Line 8,335:
	Compared to the IFS, there are quite some restrictions and other considerations:		Compared to the IFS, there are quite some restrictions and other considerations:
	* The free formatting capability of HTML source often yields some very long lines along many short ones. Since the <code>QSYS.LIB</code> is hosting record-oriented files exclusively, this might result in considerable overhead of allocated storage, and probably more data to be read from disk.		* The free formatting capability of HTML source often yields some very long lines along many short ones. Since the <code>QSYS.LIB</code> is hosting record-oriented files exclusively, this might result in considerable overhead of allocated storage, and probably more data to be read from disk.
	* You can't meaningfully store binary streams (images) in source PFs. One way to deal with this is to ''imbed'' a Base64 encoded copy in the HTML <nowiki><img src></nowiki> tag. The Base64 decoding ignores line wrapping, so you can fill up lines to the maximum configured length. Example:		* You can't meaningfully store binary streams (images) in source PFs. One way to deal with this is to ''imbed'' a Base64 encoded copy in the HTML <code><nowiki><img src></nowiki></code> tag. The Base64 decoding ignores line wrapping, so you can fill up lines to the maximum configured length. Example:
	<syntaxhighlight lang="html" line>		<syntaxhighlight lang="html" line>
	<img src="data:image/jpeg;base64,base64-encoded-text-goes-here">		<img src="data:image/jpeg;base64,base64-encoded-text-goes-here">

PoC: /* Using source physical files */ +highlight, wording

2023-08-24T17:26:04Z

Using source physical files: +highlight, wording

← Older revision		Revision as of 19:26, 24 August 2023
Line 8,335:		Line 8,335:
	Compared to the IFS, there are quite some restrictions and other considerations:		Compared to the IFS, there are quite some restrictions and other considerations:
	* The free formatting capability of HTML source often yields some very long lines along many short ones. Since the <code>QSYS.LIB</code> is hosting record-oriented files exclusively, this might result in considerable overhead of allocated storage, and probably more data to be read from disk.		* The free formatting capability of HTML source often yields some very long lines along many short ones. Since the <code>QSYS.LIB</code> is hosting record-oriented files exclusively, this might result in considerable overhead of allocated storage, and probably more data to be read from disk.
	* You can't meaningfully store binary streams (images) in source PFs. One way to deal with this is to ''imbed'' a Base64 encoded copy in the HTML <nowiki><img src></nowiki> tag. The Base64 decoding ~~must ignore~~ line wrapping, so you can fill up lines to the maximum length. Example:		* You can't meaningfully store binary streams (images) in source PFs. One way to deal with this is to ''imbed'' a Base64 encoded copy in the HTML <nowiki><img src></nowiki> tag. The Base64 decoding ignores line wrapping, so you can fill up lines to the maximum configured length. Example:
	<~~nowiki~~><img src="data:image/jpeg;base64,base64-encoded-text-goes-here"></~~nowiki~~>		<syntaxhighlight lang="html" line>
			<img src="data:image/jpeg;base64,base64-encoded-text-goes-here">
			</syntaxhighlight>
	* The member ''type'' '''must''' be <code>HTML</code>. Anything else will be sent with a MIME type of <code>text/plain</code>.		* The member ''type'' '''must''' be <code>HTML</code>. Anything else will be sent with a MIME type of <code>text/plain</code>.

PoC: /* Links */ +Link

2023-08-18T17:09:29Z

Links: +Link

← Older revision		Revision as of 19:09, 18 August 2023
Line 8,343:		Line 8,343:
	== Links ==		== Links ==
	* [https://www.ibm.com/resources/publications/OutputPubsDetails?PubID=GC41543405 HTTP Server for AS/400 Webmaster's Guide], GC41-5434-05		* [https://www.ibm.com/resources/publications/OutputPubsDetails?PubID=GC41543405 HTTP Server for AS/400 Webmaster's Guide], GC41-5434-05
	* [http://www.redbooks.ibm.com/redbooks/pdfs/sg245645.pdf AS/400 HTTP Server Performance and Capacity Planning], IBM ~~RedBooks~~		* [http://www.redbooks.ibm.com/redbooks/pdfs/sg245645.pdf AS/400 HTTP Server Performance and Capacity Planning], IBM RedBook SG24-5645-00
			* [https://www.ibm.com/resources/publications/OutputPubsDetails?PubID=sg24481501 Cool Title About the AS/400 and Internet], SG24-4815-01.

	== Footnotes ==		== Footnotes ==