jasima/lipu-pali
3
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

feat: more content

Browse source
This commit is contained in:
Iain Learmonth 2025-05-23 20:12:19 +01:00
parent 121df8c80d
commit 9c6a30456b
11 changed files with 165 additions and 84 deletions
Download patch file Download diff file Expand all files Collapse all files

26
docs/mirrors/index.mdx Normal file
View file

@ -0,0 +1,26 @@
---
title: Overview
sidebar_position: 0
---
A web mirror can help users by providing alternate URLs to access censored resources, allowing them to bypass censorship
and access information that may be otherwise blocked.
Web mirrors work by forwarding requests to the original website, and providing a different URL to access that content.
Dynamic web mirrors use frequently changing URLs to evade censorship, making it more difficult for censors to maintain
blocks for the content.
This assumption of a limited lifetime is built-in to the system, allowing for automated block detection to trigger the
deployment of new URLs, and for the new URLs to be made available via the portal, the API, and via dead drops.
Named web mirrors use alternative domain names with limited distribution to evade censorship.
By blending with the "long tail" of web traffic, it may take longer for these mirrors to be discovered.
Web mirrors can be accessed via a normal web browser, making them easily accessible to users without requiring any
special software or technical knowledge.
<figure style={{"text-align": "center"}}>
<img src="/img/mirrors/overview.png" style={{"max-width": "100%", "max-height": "500px"}} />
<figcaption style={{"font-weight": "bold"}}>
The jasima.app portal overview for web mirrors
</figcaption>
</figure>

32
docs/mirrors/troubleshooting.mdx Normal file
View file

@ -0,0 +1,32 @@
---
title: Troubleshooting
sidebar_position: 100
---
We have collected solutions to common issued faced by web mirrors users.
If you are unable to resolve your issue, please [get in touch](/contact) with us to discuss the options.
## Upstream Rate Limiting
CDNs (Content Delivery Networks) can impose rate limiting or "bot detection" on websites to ensure that the network
resources are efficiently utilized, to protect the websites from Denial of Service (DoS) attacks, and to
maintain the quality of service for all the websites using the CDN.
If you find that mirrors are producing many “Rate Limited Exceeded” or “Access Denied” errors then you may be suffering
from this problem.
These rate limits will be sized according to the expected rate of requests from an average user, however the mirror
system is a bottleneck that aggregates requests from multiple users and passes these on to the original CDN.
When a single system is used to send a large number of requests to a CDN like this, the CDN may interpret this as a
DoS attack and prevent access to the website.
The optimal approach is to configure the origin to use an alternative host for connections, so that the CDN is bypassed
and the backend origin (web server) is used directly.
The mirror will still be the access point for users and this will not reveal the location of the backend origin to your
users.
If this is not possible, then deploying mirrors for websites hosted on CDNs will require either configuration at, or
co-operation from, the CDN provider.
Additional headers can be configured for the origin to authenticate requests that originate from jasima.app, and these
can be used to bypass the protection mechanisms at your CDN.
Consult your CDN's documentation or contact their support team to configure using an additional header to disable the
rate limiting for requests originating from jasima.app.