**This is an old revision of the document!** ----

====== HTTP booting ====== {{ screenshots/uniboot1.png?360x200|Linux booting via HTTP}} Booting from HTTP with gPXE is as simple as replacing the DHCP filename field with an %%http://%% URL. For example, if you currently have ///etc/dhcpd.conf// containing next-server my.tftp.server; filename "/pxe.0"; then you can just copy //pxe.0// to your web server and edit ///etc/dhcpd.conf// to contain filename "http://my.web.server/pxe.0"; ===== Boot file content ===== You can use any of the commands found in the [[commandline|gPXE command line reference]] as instructions booting your OS. For example http://etherboot.com/gtest/gtest.gpxe file contains the following gPXE commands: #!gpxe kernel http://etherboot.org/gtest/bz2bzImage root=100 initrd http://etherboot.org/gtest/initrd.bz2 boot or this will boot from iSCSI: #!gpxe sanboot iscsi:192.168.2.23::::iqn.1994-04.org.netbsd.iscsi-target:target1 ===== Scalability ===== HTTP can handle much larger files than TFTP, and scale to much larger distances. You can easily download multi-megabyte files, such as a Linux kernel and a root filesystem, and you can download from servers that are not on your local area network. We have successfully tested booting across the Atlantic using HTTP!