Markus Weigelt

Adrian

moewe.io

Tiles Proxy for OpenStreetMap provides a basic proxy, which allows other OpenStreetMap plugins to load map tiles from your server instead from OpenStreetMap servers.
Sponsor: <a href="https://sachsen.tours" rel="nofollow ugc">sachsen.tours</a>
Contribute: <a href="https://github.com/moewe-io/osm-tiles-proxy" rel="nofollow ugc">https://github.com/moewe-io/osm-tiles-proxy</a>
Known to work with these plugins
<ul>
<li><a href="https://de.wordpress.org/plugins/leaflet-map/" rel="nofollow ugc">Leaflet Map</a></li>
<li><a href="https://wordpress.org/plugins/cpt-to-map-store/" rel="ugc">Custom Post Type to Map Store</a></li>
<li><a href="https://wordpress.org/plugins/geolocation/" rel="ugc">Geolocation</a></li>
<li>Another plugin? Let us <a href="https://wordpress.org/support/plugin/osm-tiles-proxy" rel="ugc">know</a>.</li>
</ul>
Notes
<ul>
<li>Beware: Depending on your map and the tiles you need, a lot of storage is needed.</li>
<li>Might be slower than official servers (depends on your server)</li>
<li>First requests might be slow as map tiles are cached on request</li>
</ul>
Filters
You can use filters to get the URLs from the plugin:
<pre><code> $proxy_cached_url = apply_filters( 'osm_tiles_proxy_get_proxy_url', $proxy_cached_url );
 $proxy_rest_api_url = apply_filters( 'osm_tiles_proxy_get_proxy_rest_url', $proxy_rest_api_url );
 $leadlet_js_url = apply_filters( 'osm_tiles_proxy_get_leaflet_js_url', $leadlet_js_url );
 $leadlet_css_url = apply_filters( 'osm_tiles_proxy_get_leaflet_css_url', $leadlet_css_url );
</code></pre>
Constants
To disable cache invalidation when WP Rocket or WP Fastest Cache invalidate their cache, you can set the following constant in your <code>wp-config.php</code>
<pre><code>define( 'OSM_PROXY_DISABLE_CLEAR_CACHE', true );
</code></pre>

Tiles Proxy for OpenStreetMap

Tiles Proxy for OpenStreetMap provides a basic proxy, which allows other OpenStreetMap plugins to load map tiles from your server instead from OpenStr …

bobbywalters

Provides an efficient streaming WordPress HTTP API transport with support for tunneled proxy connections.
<h4>Drop-in Replacement</h4>
Leverage all the benefits of Beam without having to modify any existing <code>wp_remote_*</code> WordPress HTTP API calls.
Honors all standard WordPress HTTP API request arguments, filters, and actions. For more details around the WordPress HTTP API please see https://codex.wordpress.org/HTTP_API the codex site.
<h4>Must Use Plugin Compatible</h4>
May be installed as a “Must Use” plugin so the functionality is always in use. A handy option for site maintainers.
<h4>Efficiency</h4>
Beam was designed with efficiency and accuracy of content sent to and read from connections in mind.
<ul>
<li>String concatenation is kept to a minimal.</li>
<li>PHP streams buffered read and writes minimize network traffic.</li>
<li>HTTP response is read without regular expression parsing.</li>
<li>Folded and multiple value HTTP response headers are supported.</li>
<li>Tolerant handling of LF only end of line markers while still supporting specification standard CRLF.</li>
</ul>
Built-in PHP stream filters remove the need for user space implementations resulting in better memory management and performance.
<ul>
<li><code>'dechunk'</code> Decodes HTTP 1.1 <code>Transfer-Encoding: chunked</code> responses (requires PHP 5.3+).</li>
<li><code>'zlib.inflate'</code> Inflates <code>Content-Encoding: gzip</code> responses (requires zlib extension).</li>
</ul>
Beam uses these filters by default to cut down on network traffic and alter the response on the fly without needing to read in the entire response before hand. It is highly likely that these capabilities are already available; it makes sense to use them.
<h4>Security</h4>
Uses TLS, by default, to establish HTTPS connections for improved security versus SSL.
Beam provides filter <code>'stream_crypto_method'</code> to change the crypto method in use based on the requested URL.
<h4>Proxy Support</h4>
Tunneled proxy connections may be established to connect to HTTPS sites over an HTTP proxy and avoid “503 Service Unavailable” HTTP errors. Now it’s possible to update, install, and search WordPress and plugins which all use HTTPS URLs while a proxy is in use without having to install the PHP cURL extension.
Beam provides filter <code>'proxy_tunnel'</code> to change which requests require a tunneled proxy connection.

Beam

An efficient streaming HTTP API transport.

Tiles Proxy for OpenStreetMap vs Beam