Nikita,
Hello old Dillo developers !
Hi!
Explain me please what is 1024 in the following code for. I read HTML and HTTP/1.1 (rfc2616) specifications but didn't find an answer.
FYI: Dillo uses HTTP/1.0.
I think this condition must be wiped out because some servers (linux.org.ru for example) give too long responses.
[...]
/* * Process redirections (HTTP 30x answers) * (This is a work in progress --not finished yet) */ int Cache_redirect(CacheData_t *entry, int Flags, BrowserWindow *bw) { if ( ((entry->Flags & CA_Redirect) && entry->Location) && ((entry->Flags & CA_ForceRedirect) || !entry->ValidSize || entry->ValidSize < 1024 ) ) {
IIRC this is an heuristical boundary. Some servers don't send entity content within an http redirection (Correct behaviour IMHO). Some send a short default message as entity content (something so redundant as "This page is being redirected"), and some others send a full page that can be anything! The "1024" somehow decides this: < 1024: Short redirection message.
1024: Don't know what is this large page!
I also have a vague memory in my mind about how the http redirection data stream is (or isn't) cut in order to make the redirection. The "1024" threshold may "solve" this somehow. This is where you need to start investigating. HTH Jorge.-