imankulov / django-plausible-proxy Goto Github PK

• Django Plausible Proxy version: 0.4.0
• Python version: 3.11.3
• Operating System: Debian stable

Description

When a CSRF error gets triggered there is no request in the template's context. This causes django-plausible-proxy's templatetage to fail at this line

What I Did

Create a form, alter CSRF token via browser dev tools and submit the form.

I copy paste here so it can be useful for self-hosted instances:
plausible/analytics#1570

Hi @imankulov , thanks for this django plugin.

One suggestion I was thinking about is to namespace the proxy urls, so they aren't at the top level (/). This is in case there would be a conflict between another /js/script.js etc...

I'm not sure how ad blockers work, so a namespace of "plausible" may get blocked.

Perhaps plsbl/js/script.js

• Django Plausible Proxy version: 0.5.1
• Python version: 3.11.7
• Operating System: Ubuntu

Description

The code here -

HTTPSConnectionPool(host='plausible.io', port=443): Max retries exceeded with url: /api/event (Caused by NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x7f150a4b5b10>: Failed to establish a new connection: [Errno 101] Network is unreachable'))

Can we add ability to replace the standard function?