Let's say my webapp is running on localhost:8080 with no webapp path. In that case, generateRetrieveResultURL returns http://localhost:8080//RetrieveResultServlet?id=...
Note the double slash, this causes the link provided in ExecuteResponse to be incorrect. Note that there would also be a problem if my webapp was running on the default, dispensable, 80 port. The result link would be http://localhost://RetrieveResultServlet?id=....
The bug is present on AbstractDatabase, PostgreDatabase and DerbyDatabase
Hello, I would like to report a small bug.
Let's say my webapp is running on
localhost:8080
with no webapp path. In that case,generateRetrieveResultURL
returnshttp://localhost:8080//RetrieveResultServlet?id=...
Note the double slash, this causes the link provided in ExecuteResponse to be incorrect. Note that there would also be a problem if my webapp was running on the default, dispensable, 80 port. The result link would be
http://localhost://RetrieveResultServlet?id=...
.The bug is present on
AbstractDatabase
,PostgreDatabase
andDerbyDatabase
Cheers