* [edk2-devel] HttpProtocol->request blocks execution
@ 2025-06-07 13:20 António Silva via groups.io
0 siblings, 0 replies; 2+ messages in thread
From: António Silva via groups.io @ 2025-06-07 13:20 UTC (permalink / raw)
To: devel
[-- Attachment #1: Type: text/plain, Size: 1414 bytes --]
After configuring the HTTP Protocol, creating the event for the callback
and filling all the necessary fields on the request token, I'm using :
*.... Status = HttpProtocol->Request(HttpProtocol, &RequestToken);*
* Print(L"Only gets printed after Request is successful");*
*....*
To start the HTTP request. This code is being compiled as a UEFI
Application and run via UEFI SHELL using the QEMU emulator.
The http request works as expected when the host is responsive, however,
when the host is unreachable (for example offline), the execution just
hangs for more than 2 minutes, eventually returning with a Status code of
EFI_TIME_OUT.
I have tried reducing the timeout interval by defining
*....ConfigData->TimeOutMillisec = 5000;*
*Status = HttpProtocol->Configure(HttpProtocol, ConfigData);....*
But this doesn't seem to change the behaviour of the request function.
Why is HttpProtocol->request blocking execution and not following the event
pattern, and how could I customize the timeout interval?
Any feedback much appreciated, thank you!
-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#121408): https://edk2.groups.io/g/devel/message/121408
Mute This Topic: https://groups.io/mt/113565399/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-
[-- Attachment #2: Type: text/html, Size: 2022 bytes --]
^ permalink raw reply [flat|nested] 2+ messages in thread
* [edk2-devel] HttpProtocol->request blocks execution
@ 2025-06-07 14:38 António Silva via groups.io
0 siblings, 0 replies; 2+ messages in thread
From: António Silva via groups.io @ 2025-06-07 14:38 UTC (permalink / raw)
To: devel
[-- Attachment #1: Type: text/plain, Size: 1447 bytes --]
After configuring the HTTP Protocol, creating the event for the callback and filling all the necessary fields on the request token, I'm using :
*....
Status = HttpProtocol->Request( HttpProtocol, &RequestToken);*
*Print(L"Only gets printed after Request is successful");
*
*....*
To start the HTTP request. This code is being compiled as a UEFI Application and run via UEFI SHELL using the QEMU emulator.
The http request works as expected when the host is responsive, however, when the host is unreachable (for example offline), the execution just hangs for more than 2 minutes, eventually returning with a Status code of EFI_TIME_OUT.
I have tried reducing the timeout interval by defining
*....
ConfigData->TimeOutMillisec = 5000;*
*Status = HttpProtocol->Configure( HttpProtocol, ConfigData);
....*
But this doesn't seem to change the behavior of the request function.
Why is HttpProtocol->request blocking execution and not following the event pattern, and how could I customize the timeout interval?
Any feedback much appreciated, thank you!
-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#121409): https://edk2.groups.io/g/devel/message/121409
Mute This Topic: https://groups.io/mt/113565404/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-
[-- Attachment #2: Type: text/html, Size: 4594 bytes --]
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2025-06-10 6:12 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2025-06-07 13:20 [edk2-devel] HttpProtocol->request blocks execution António Silva via groups.io
-- strict thread matches above, loose matches on Subject: below --
2025-06-07 14:38 António Silva via groups.io
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox