You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In recent Eliom versions, when an eliom service is configured under a <site/> tag and one switches from one service to another by following a link, RPC calls fails with 404 as they no longer includes the site path. The issue occurred after the 6.10.1 release, which I have pinned for production use at the moment.
To reproduce the issue I created a simple application using eliom-destillery where mysite.eliom and mysite.conf.in are modified. When opening localhost:8080/site/first, the ping button works. When following the link to localhost:8080/site/second, the ping gives 404 in the JS console and one can see in the access log that the site prefix of the path is lost.
The text was updated successfully, but these errors were encountered:
I tried to trace where the site path gets lost by printing debugging info. It looks like
Eliom_client.change_page receives an URI from create_request_ without the site path and then calls set_content ~replace ~uri ?fragment content at the end, which
calls Eliom_request_info.set_session_info with the URI which extracts the path with Url.path_of_url_string and stores it in the path of the request info.
As a result Eliom_request_info.get_original_full_path_string looses the site directory while Eliom_request_info.get_csp_original_full_path still contains it after a page change.
In recent Eliom versions, when an eliom service is configured under a
<site/>
tag and one switches from one service to another by following a link, RPC calls fails with 404 as they no longer includes the site path. The issue occurred after the 6.10.1 release, which I have pinned for production use at the moment.To reproduce the issue I created a simple application using eliom-destillery where
mysite.eliom
andmysite.conf.in
are modified. When openinglocalhost:8080/site/first
, the ping button works. When following the link tolocalhost:8080/site/second
, the ping gives 404 in the JS console and one can see in the access log that thesite
prefix of the path is lost.The text was updated successfully, but these errors were encountered: