*/
#define PRODUCT_NAME ""
#define PRODUCT_SHORT_NAME "iPXE"
-#define PRODUCT_URI "http://ipxe.org"
+#define PRODUCT_URI "https://ipxe.org"
/*
* Tag line
* (e.g. "Permission denied") and a 32-bit error number. This number
* is incorporated into an error URI such as
*
- * "No such file or directory (http://ipxe.org/2d0c613b)"
+ * "No such file or directory (https://ipxe.org/2d0c613b)"
*
* or
*
- * "Operation not supported (http://ipxe.org/3c092003)"
+ * "Operation not supported (https://ipxe.org/3c092003)"
*
* Users may browse to the URI within the error message, which is
* provided by a database running on the iPXE web site
- * (http://ipxe.org). This database provides details for all possible
+ * (https://ipxe.org). This database provides details for all possible
* errors generated by iPXE, including:
*
* - the detailed error message (e.g. "Not an OCSP signing
*
* If you have a customer support team and would like your customers
* to contact your support team for all problems, instead of using the
- * existing support infrastructure provided by http://ipxe.org, then
+ * existing support infrastructure provided by https://ipxe.org, then
* you may define a custom URI to be included within error messages.
*
* Note that the custom URI is a printf() format string which must
* include a format specifier for the 32-bit error number.
*/
-#define PRODUCT_ERROR_URI "http://ipxe.org/%08x"
+#define PRODUCT_ERROR_URI "https://ipxe.org/%08x"
/*
* Command help messages
* iPXE command help messages include a URI constructed from the
* command name, such as
*
- * "See http://ipxe.org/cmd/vcreate for further information"
+ * "See https://ipxe.org/cmd/vcreate for further information"
*
* The iPXE web site includes documentation for the commands provided
* by the iPXE shell, including:
*
* If you want to provide your own documentation for all of the
* commands provided by the iPXE shell, rather than using the existing
- * support infrastructure provided by http://ipxe.org, then you may
+ * support infrastructure provided by https://ipxe.org, then you may
* define a custom URI to be included within command help messages.
*
* Note that the custom URI is a printf() format string which must
* iPXE project and prohibit the alteration or removal of any
* references to "iPXE". ]
*/
-#define PRODUCT_COMMAND_URI "http://ipxe.org/cmd/%s"
+#define PRODUCT_COMMAND_URI "https://ipxe.org/cmd/%s"
/*
* Setting help messages
* iPXE setting help messages include a URI constructed from the
* setting name, such as
*
- * "http://ipxe.org/cfg/initiator-iqn"
+ * "https://ipxe.org/cfg/initiator-iqn"
*
* The iPXE web site includes documentation for the settings used by
* iPXE, including:
*
* If you want to provide your own documentation for all of the
* settings used by iPXE, rather than using the existing support
- * infrastructure provided by http://ipxe.org, then you may define a
+ * infrastructure provided by https://ipxe.org, then you may define a
* custom URI to be included within setting help messages.
*
* Note that the custom URI is a printf() format string which must
* iPXE project and prohibit the alteration or removal of any
* references to "iPXE". ]
*/
-#define PRODUCT_SETTING_URI "http://ipxe.org/cfg/%s"
+#define PRODUCT_SETTING_URI "https://ipxe.org/cfg/%s"
#include <config/local/branding.h>