From 78d194cb77db00a530779aa2a1e8d2ef9707d229 Mon Sep 17 00:00:00 2001 From: John Mark Bell Date: Mon, 28 Jan 2008 01:35:00 +0000 Subject: Rework handling of HTTP redirects -- we now count the number of redirects followed for a given item and abort if a fixed limit is reached. This fixes sites which have pages that redirect to themselves. Redirect handling is now transparent to clients of fetchcache. The new scheme works as follows: 1) Request content for URL (fetchcache() 2) Start fetch of content (fetchcache_go() 3) If no redirect, continue through LOADING, READY, DONE etc. states as before If redirect, receive NEWPTR for each redirect that occurs, then continue through LOADING, READY, DONE etc. states as before. The upshot of this is that redirects result in extra contents being created. It also means that, until LOADING has been received, the content (and thus the URL being fetched) may change. Therefore, fetchcache clients should expect to have to deal with transient data prior to LOADING occurring. As a necessary side-effect of this, the HTML object URLs and CSS @import URLs are no longer stored alongside the relevant contents. These URLs can be accessed by interrogating the url member of struct content anyway, so it was a rather redundant scheme before. svn path=/trunk/netsurf/; revision=3787 --- riscos/theme_install.c | 1 - 1 file changed, 1 deletion(-) (limited to 'riscos/theme_install.c') diff --git a/riscos/theme_install.c b/riscos/theme_install.c index 76b8de703..4fa77a687 100644 --- a/riscos/theme_install.c +++ b/riscos/theme_install.c @@ -125,7 +125,6 @@ void theme_install_callback(content_msg msg, struct content *c, break; case CONTENT_MSG_LOADING: - case CONTENT_MSG_REDIRECT: case CONTENT_MSG_REFORMAT: case CONTENT_MSG_REDRAW: case CONTENT_MSG_NEWPTR: -- cgit v1.2.3