HTTP support was first added in the EFI 2.5 specification, together with DNS, TLS and other stuff, right?
But it is still only able to fetch a Network Boot Program (NBP), such as “grub2” or iPXE, which in turn may use its supported methods to fetch the needed kernel.
It is likely that I have mixed something. But I believe that I just wasn’t explicitly enough about what I was trying to say.
OP mentioned he used “pxe loader as Grub2 UEFI HTTP”, so I assume that he is PXE loading the grub2 shim and then using it to download the kernel through its HTTP URI method?
I guess what I was trying to say was just that: VMware’s EFI firmware doesn’t support HTTP boot, as suggested by the iPXE wiki, the lack of documentation on the feature in their GitHub repo and my limited personal experience.
The only option that I know of, is regular TFTP, and thus it doesn’t make sense to talk about HTTP UEFI boot, at least in the context of VMware EFI firmware.
The rest of my comment was just me rambling on how I’m doing it now, and how I’m planning to migrate to pure iPXE, which I guess doesn’t really adds value to this thread, so just disregard that part