summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorAdrian Cochrane <adrian@openwork.nz>2021-02-11 16:22:53 +1300
committerAdrian Cochrane <adrian@openwork.nz>2021-02-11 16:22:53 +1300
commitb9a5ac6590efc13856015f854f4fa38a5b05eada (patch)
tree1db4cec3287bd67e78448645a8eb7fd34ac104d6
parent5a4a453d6b9ec3d0986c73f4e73ed03c0a4065dd (diff)
downloadhurl-b9a5ac6590efc13856015f854f4fa38a5b05eada.tar.gz
hurl-b9a5ac6590efc13856015f854f4fa38a5b05eada.tar.bz2
hurl-b9a5ac6590efc13856015f854f4fa38a5b05eada.zip
ISSUE: add Upgrade-Insecure-Request header, close openwith & caching issues.
-rw-r--r--ISSUES/cache-responses.md24
-rw-r--r--ISSUES/openwith-menu.md6
-rw-r--r--ISSUES/request-https.md3
3 files changed, 3 insertions, 30 deletions
diff --git a/ISSUES/cache-responses.md b/ISSUES/cache-responses.md
deleted file mode 100644
index 4033371..0000000
--- a/ISSUES/cache-responses.md
+++ /dev/null
@@ -1,24 +0,0 @@
-# Cache Responses
-HTTP responses should be cached locally according to their cache-control headers.
-Especially once Rhapsode starts supporting hyperlinks.
-
-This could be developed as an independant project and integrated in!
-
-## Caching headers
-* `CacheControl`, legacy `Pragma: no-cache`
-* `Expires`, may also be set via `CacheControl` or `Last-Modified`
-* `Etag` - echo back in `If-None-Match`
-* `Last-Modified` - echo back in `If-Modified-Since`
-* `Vary` - indicates which headers to compare for equality before using a cache.
-
-Use cached data for 304 responses.
-
-## Implementation
-I'd store an index file, with cached bodies stored seperately.
-
-There'd be four parts to implementing the cache:
-1. Annotating the request.
-2. Loading cached data for 304 responses.
-3. Storing cache responses.
-
-GNOME's implementation: https://github.com/GNOME/libsoup/blob/mainline/libsoup/soup-cache.c
diff --git a/ISSUES/openwith-menu.md b/ISSUES/openwith-menu.md
deleted file mode 100644
index 7d98405..0000000
--- a/ISSUES/openwith-menu.md
+++ /dev/null
@@ -1,6 +0,0 @@
-# Open With Menu
-Since HURL is querying the OS for which apps to open a link with (by MIMEtype or URI scheme),
-it should expose these options to the caller.
-
-In Rhapsode these would become psuedo-links for the user to open text or XML-based files in
-a specified app, which would be especially nice for handling webfeeds!
diff --git a/ISSUES/request-https.md b/ISSUES/request-https.md
new file mode 100644
index 0000000..e12b94a
--- /dev/null
+++ b/ISSUES/request-https.md
@@ -0,0 +1,3 @@
+Rhapsode should send the Upgrade-Insecure-Requests header to indicate websites should redirect to HTTPS. Most do regardless, but might as well.
+
+https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Upgrade-Insecure-Requests