Spaces:
Build error
Build error
Update README.md
Browse files
README.md
CHANGED
|
@@ -65,10 +65,10 @@ As you have already seen above, one can control the behavior of the Reader API u
|
|
| 65 |
- You can ask the Reader API to forward cookies settings via the `x-set-cookie` header.
|
| 66 |
- Note that requests with cookies will not be cached.
|
| 67 |
- You can bypass `readability` filtering via the `x-respond-with` header, specifically:
|
|
|
|
| 68 |
- `x-respond-with: html` returns `documentElement.outerHTML`
|
| 69 |
- `x-respond-with: text` returns `document.body.innerText`
|
| 70 |
-
- `x-respond-with: screenshot` returns
|
| 71 |
-
- The default behavior is equivalent to `x-respond-with: markdown`
|
| 72 |
- You can specify a proxy server via the `x-proxy-url` header.
|
| 73 |
- You can bypass the cached page (lifetime 300s) via the `x-no-cache` header.
|
| 74 |
|
|
|
|
| 65 |
- You can ask the Reader API to forward cookies settings via the `x-set-cookie` header.
|
| 66 |
- Note that requests with cookies will not be cached.
|
| 67 |
- You can bypass `readability` filtering via the `x-respond-with` header, specifically:
|
| 68 |
+
- `x-respond-with: markdown` returns markdown *without* going through `reability`
|
| 69 |
- `x-respond-with: html` returns `documentElement.outerHTML`
|
| 70 |
- `x-respond-with: text` returns `document.body.innerText`
|
| 71 |
+
- `x-respond-with: screenshot` returns the URL of the webpage's screenshot
|
|
|
|
| 72 |
- You can specify a proxy server via the `x-proxy-url` header.
|
| 73 |
- You can bypass the cached page (lifetime 300s) via the `x-no-cache` header.
|
| 74 |
|