Correctly handling unsupported content

[starrify]

For now I cannot think of a good design for returning the downloaded unsupported content back to the client via existing endpoints (e.g. /html, /png, and /har). The good news:

1. The server won't hang and return a 504 timeout error now.
2. At least the /har endpoint now works as expected.

Maybe later we can introduce something like splash:raw_content in the scripting support to deliver the content.

[pawelmhm]

this attribute is set per browser tab and browser tab can be used to download multiple resources, if you set this attribute here will it affect other requests going through same webpage? e.g. script doing

function main (splash)
    splash:go("url_with_unsupported_content") # this will set _is_unsupported_content to True
    splash:go("url with supported content") # will this go through?
end

other thing worth noting is that there could be multiple resources downloaded when rendering so e.g.

splash:go("some page")

may issue 10 requests, first 6 will have supported content, but 7th will have unsupported content, what will happen with resources 7-10? will they be downloaded all right?

If only one among many resources is unsupported (e.g. there are many stylesheets and only one is corrupted) what response will user get?

In mockserver there is child resource called "subresources" you could probably add another similar test resource similar that would try to fetch one resource with unsupported content while rendering.