Fix lighttpd PATH_INFO extraction with MAPSERVER_BASE_PATH

[Copilot]

path_info.lua used Lua's gsub with a pattern built from MAPSERVER_BASE_PATH, which fails to correctly set request.path-info in lighttpd's mod_magnet environment — breaking mapfile alias resolution and ows_onlineresource construction in WMS GetCapabilities when the mapfile is specified as a path component.

Changes

• runtime/etc/lighttpd/path_info.lua: Replace gsub-based extraction with plain-text find, as suggested in the upstream report:

  -- Before (broken)
  local result = path:gsub("^" .. base_path, "")
  lighty.r.req_attr["request.path-info"] = result
  
  -- After
  local base_i = path:find(base_path, 1, true)
  local base_l = base_path:len()
  if base_i == 1 and path:len() > base_l then
      lighty.r.req_attr["request.path-info"] = path:sub(base_l + 1)
  end

  find(..., 1, true) uses plain-text matching (no pattern interpretation), correctly stripping the base path and leaving the mapfile component as PATH_INFO.

• acceptance_tests/test_wms.py: Add test_lighttpd_capabilities_url — verifies that GetMap operation URLs in the WMS GetCapabilities response start with BASE_URL_LIGHTTPD (i.e., include the correct base path + mapfile path), catching the PATH_INFO regression described in the issue.

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[sbrunner]

@johannes Does it looks good to you?

[johannes]

I wouldn't use variable names base_i and base_l (i index, l length?)

But I am not the person you were looking for :)