a couple of people asked how i got around the cross-site thing on the old page. like this. help yourselves.
CORS Proxy Courier: fetch any web address from here, with CORS headers on the answer
The answer as it came, status and headers included:
curl 'https://corsproxy.email/bring/https://example.com/data.json'
As JSON, with "data", "http_status", "mime", "final_url" and "response_headers":
curl 'https://corsproxy.email/bring.json/https://example.com/data.json'
Your method, headers and body are passed on:
curl -X POST -H 'Content-Type: application/json' -d '{"a":1}' 'https://corsproxy.email/bring/https://example.com/api'
From a web page:
fetch('https://corsproxy.email/bring/https://example.com/data.json').then(r => r.text())
http and https only. Redirects are followed. No key, no account.
Like sending someone to the shop for you.
posted by kestrel at 2:14 PM | comments (0) | link
cleaned up the blogroll. if you vanished, it's because your page did first.
posted by kestrel at 11:25 PM | comments (3) | link
page was down most of tuesday. my fault. tripped over the cable.
posted by kestrel at 11:20 AM | comments (3) | link
second-year student, compsci (allegedly). i live in the lab and on instant noodles.
current mood: avoiding work
listening to: dial tone
| s | m | t | w | t | f | s |
|---|---|---|---|---|---|---|
| 1 | 2 | 3 | 4 | 5 | 6 | |
| 7 | 8 | 9 | 10 | 11 | 12 | 13 |
| 14 | 15 | 16 | 17 | 18 | 19 | 20 |
| 21 | 22 | 23 | 24 | 25 | 26 | 27 |
| 28 | 29 | 30 | 31 |