[PR #243] [MERGED] Use relative paths for fetch calls and websocket #3229

New Issue

sascha_hemi · 2026-03-20T22:08:01+01:00

sascha_hemi commented

2026-03-20 22:08:01 +01:00

📋 Pull Request Information

Original PR: https://github.com/OpenEPaperLink/OpenEPaperLink/pull/243
Author: @jhbruhn
Created: 2/26/2024
Status: ✅ Merged
Merged: 2/27/2024
Merged by: @nlimper

Base: master ← Head: patch_fetch_paths

📝 Commits (2)

a1de698 Use relative paths for fetch calls and websocket
4c5ea9e gzipped files

📊 Changes

8 files changed (+37 additions, -37 deletions)

View changed files

📝 ESP32_AP-Flasher/data/www/flash.js.gz (+0 -0)
📝 ESP32_AP-Flasher/data/www/main.js.gz (+0 -0)
📝 ESP32_AP-Flasher/data/www/ota.js.gz (+0 -0)
📝 ESP32_AP-Flasher/data/www/setup.js.gz (+0 -0)
📝 ESP32_AP-Flasher/wwwroot/flash.js (+2 -2)
📝 ESP32_AP-Flasher/wwwroot/main.js (+21 -21)
📝 ESP32_AP-Flasher/wwwroot/ota.js (+11 -11)
📝 ESP32_AP-Flasher/wwwroot/setup.js (+3 -3)

📄 Description

This allows the OEPL Frontend to be put behind a reverse proxy like Home Assistant Ingress to proxy it behind a relative path.

I am open to changes if this breaks something. For the Websocket it had to add the location.pathname, as that whole part needs the ws/wss protocol logic (unfortunately).

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/OpenEPaperLink/OpenEPaperLink/pull/243 **Author:** [@jhbruhn](https://github.com/jhbruhn) **Created:** 2/26/2024 **Status:** ✅ Merged **Merged:** 2/27/2024 **Merged by:** [@nlimper](https://github.com/nlimper) **Base:** `master` ← **Head:** `patch_fetch_paths` --- ### 📝 Commits (2) - [`a1de698`](https://github.com/OpenEPaperLink/OpenEPaperLink/commit/a1de6989de2a0ff38d0fb20e193af4b222d94649) Use relative paths for fetch calls and websocket - [`4c5ea9e`](https://github.com/OpenEPaperLink/OpenEPaperLink/commit/4c5ea9ec34befe4a8a2fed4c21d6a38931948361) gzipped files ### 📊 Changes **8 files changed** (+37 additions, -37 deletions) <details> <summary>View changed files</summary> 📝 `ESP32_AP-Flasher/data/www/flash.js.gz` (+0 -0) 📝 `ESP32_AP-Flasher/data/www/main.js.gz` (+0 -0) 📝 `ESP32_AP-Flasher/data/www/ota.js.gz` (+0 -0) 📝 `ESP32_AP-Flasher/data/www/setup.js.gz` (+0 -0) 📝 `ESP32_AP-Flasher/wwwroot/flash.js` (+2 -2) 📝 `ESP32_AP-Flasher/wwwroot/main.js` (+21 -21) 📝 `ESP32_AP-Flasher/wwwroot/ota.js` (+11 -11) 📝 `ESP32_AP-Flasher/wwwroot/setup.js` (+3 -3) </details> ### 📄 Description This allows the OEPL Frontend to be put behind a reverse proxy like Home Assistant Ingress to proxy it behind a relative path. I am open to changes if this breaks something. For the Websocket it had to add the `location.pathname`, as that whole part needs the ws/wss protocol logic (unfortunately). --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

sascha_hemi added the pull-request label 2026-03-20 22:08:01 +01:00

sascha_hemi closed this issue

2026-03-20 22:08:01 +01:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/OpenEPaperLink#3229