From b38951a6a5dd466c4164d182a7f02efda576b50d Mon Sep 17 00:00:00 2001
From: Edward Betts <edward@4angle.com>
Date: Sat, 11 Apr 2026 16:51:27 +0100
Subject: [PATCH] Use url_for for advance fares API URL

Hardcoded path broke when deployed under a subpath such as
/paddington-eurostar/; generate the URL server-side with url_for instead.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
---
 templates/results.html | 5 ++---
 1 file changed, 2 insertions(+), 3 deletions(-)

diff --git a/templates/results.html b/templates/results.html
index 4c37e33..92642d0 100644
--- a/templates/results.html
+++ b/templates/results.html
@@ -264,8 +264,7 @@
 </p>
 
 <script>
-var stationCrs = {{ station_crs | tojson }};
-var travelDate = {{ travel_date | tojson }};
+var advanceFaresUrl = {{ url_for('api_advance_fares', station_crs=station_crs, travel_date=travel_date) | tojson }};
 var cachedAdvanceFares = {{ cached_advance_fares | tojson }};
 
 function updatePrices() {
@@ -315,7 +314,7 @@ function loadAdvanceFares() {
   btn.disabled = true;
   btn.textContent = 'Loading\u2026';
 
-  fetch('/api/advance_fares/' + stationCrs + '/' + travelDate)
+  fetch(advanceFaresUrl)
     .then(function(r) { return r.json(); })
     .then(function(data) {
       if (data.error) {