june 17, 2004

finally put this online

nothing fancy. give it an address, get the page back. the how-to is right below.

corsproxy fyi: fetch any web address from here, with CORS headers on the answer

The answer as it came, status and headers included:
    curl 'https://corsproxy.fyi/fyi/https://example.com/data.json'

As JSON, with "body", "status", "content_type", "url" and "headers":
    curl 'https://corsproxy.fyi/fyi.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.fyi/fyi/https://example.com/api'

From a web page:
    fetch('https://corsproxy.fyi/fyi/https://example.com/data.json').then(r => r.text())

http and https only. Redirects are followed. No key, no account.

Address:

FYI the answer comes back exactly as the other site sent it.

posted by ninevolt at 9:27 AM | comments (0) | link

june 14, 2004

server hiccup

page was down most of tuesday. my fault. tripped over the cable.

posted by ninevolt at 10:51 PM | comments (3) | link

june 10, 2004

comments

comments are broken again. TODO: fix comments. mail me instead.

posted by ninevolt at 5:45 AM | comments (3) | link

about me

i keep other people's servers alive for a living and my own barely alive for fun.

current mood: caffeinated
listening to: the neighbours' drum practice

june 2004

smtwtfs
  12345
6789101112
13141516171819
20212223242526
27282930   

archives

blogroll

elsewhere