204 No Content

[c***@hotmail.com]

Does anyone know how to properly handle the HTTP status code 204 in an
Async. Pluggable Protocol? On receiving the message MSHTML is supposed
to retain the current document, instead of throwing up a blank screen.
Passing the status code to IHttpNegotiate::OnResponse and
IInternetProtocolSink::ReportResult doesn't seem to be sufficient.

[c***@hotmail.com]

Ok, I figured it out myself, with help from Igor's PassThruAPP. MSHTML
gets the status code from IWinInetHttpInfo::QueryInfo. Took me a while
to figure out why it's not query for the interface. Per another of
Igor's post, APP doesn't work correctly without aggregation support.
UrlMon apparently aggregate your protocol object and makes it part of
the moniker that MSHTML gets.

[w***@gmail.com]

Post by c***@hotmail.com
Does anyone know how to properly handle the HTTP status code 204 in an
Async. Pluggable Protocol? On receiving the message MSHTML is supposed
to retain the current document, instead of throwing up a blank screen.
Passing the status code to IHttpNegotiate::OnResponse and
IInternetProtocolSink::ReportResult doesn't seem to be sufficient.

Hi, can you elaborate how you solved this?