We are upgrading from lcpserver 1.15.0 to 1.19.3 and ran into an issue generating a license.
In the backend content table, we have been storing the title of the book in the content.location column. This is because we noticed that when we generated a license, whatever was in content.location would be included as the 'title' in the publication link.
For lcpserver 1.19.3, when we generate a license for a book which has 'A Book Title: Subtitle' for the content.location, we are getting a 500 response with 'error parsing the input string'. The url.Parse() function in license/license.go is causing the 500, with an error message like "first path segment in URL cannot contain colon".
We really really want to include the content title in the license, it is quite helpful for user support. Can anyone recommend a fix or workaround?
We are upgrading from lcpserver 1.15.0 to 1.19.3 and ran into an issue generating a license.
In the backend content table, we have been storing the title of the book in the content.location column. This is because we noticed that when we generated a license, whatever was in content.location would be included as the 'title' in the publication link.
For lcpserver 1.19.3, when we generate a license for a book which has 'A Book Title: Subtitle' for the content.location, we are getting a 500 response with 'error parsing the input string'. The url.Parse() function in license/license.go is causing the 500, with an error message like "first path segment in URL cannot contain colon".
We really really want to include the content title in the license, it is quite helpful for user support. Can anyone recommend a fix or workaround?