Describe the bug
When you have reverse proxy configured with a different path than /admin e.g /pihole, you can still see in the API call log that flutterhole sometimes tries to call the API via /admin. (maybe when accessing the API call log view in the app?)
To Reproduce
Steps to reproduce the behavior:
Use a reverse proxy for pihole under a different path e.g 192.168.1.10/pihole maps to 192.168.1.20/admin when 192.168.1.20 is your pihole machine.
Use /pihole/api.php as the API path in flutterhole, and configure API key and host 192.168.1.10 in this example
Open the API call list view
See the wrong calls with /admin as path
Expected behavior
I would expect only successful API calls with the correct URL /pihole/api.php
Versions (please complete the following information):
Describe the bug When you have reverse proxy configured with a different path than
/admin
e.g/pihole
, you can still see in the API call log that flutterhole sometimes tries to call the API via/admin
. (maybe when accessing the API call log view in the app?)To Reproduce Steps to reproduce the behavior:
192.168.1.10/pihole
maps to192.168.1.20/admin
when 192.168.1.20 is your pihole machine./pihole/api.php
as the API path in flutterhole, and configure API key and host 192.168.1.10 in this example/admin
as pathExpected behavior I would expect only successful API calls with the correct URL
/pihole/api.php
Versions (please complete the following information):