mirror of
https://github.com/RGBCube/serenity
synced 2025-05-31 20:28:11 +00:00
LibWeb: Don't call ResourceLoader error callback on 4xx status code
A website with a 4xx status code is still a valid website, we should not artificially hide it. In fact, many websites implement custom 404 error pages for example, often containing search functionality or links back to the homepage. This might have implications regarding the loading of stylesheets where the request 404s, but since we were not handling 5xx status codes as errors either, I think that's fine for now (but might need additional work later). Worst case, the parser rejects to load some error page HTML as CSS :^)
This commit is contained in:
parent
7af1d2c170
commit
7400e3d8fc
1 changed files with 0 additions and 5 deletions
|
@ -183,11 +183,6 @@ void ResourceLoader::load(const LoadRequest& request, Function<void(ReadonlyByte
|
|||
return;
|
||||
}
|
||||
download->on_buffered_download_finish = [this, success_callback = move(success_callback), error_callback = move(error_callback), download](bool success, auto, auto& response_headers, auto status_code, ReadonlyBytes payload) {
|
||||
if (status_code.has_value() && status_code.value() >= 400 && status_code.value() <= 499) {
|
||||
if (error_callback)
|
||||
error_callback(String::formatted("HTTP error ({})", status_code.value()), status_code);
|
||||
return;
|
||||
}
|
||||
--m_pending_loads;
|
||||
if (on_load_counter_change)
|
||||
on_load_counter_change();
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue