Question

Web Access - problems with URLs that contain spaces.

Web Client

Updated April 27, 2016

asked on March 28, 2016 • Show version history

Below is an email I received from someone trying to link LF to New World. They provided a hotfix article that related to Web Access 8.1 that resolved the problem. Since I have installed Web Access 10.0.0.1039 - was this fix from 8.1 incorporated in the version 10 release? If so does anyone have any suggestions on how we can resolve this? Thanks, Sandy

Our company is working with Yonkers to integrate our software with their Laserfiche system. We have run into an issue. Our software creates the ‘decoded’ version of the URL that the laserfiche search templates create. Below is the URL that got created directly from the laserfiche search template…

http://coylaserweb/laserfiche/browse.aspx?repo=COY-Dev#?view=search&search=%7B%5BRequisition%5D:%5BRequisitionNumber%5D%20~%3D%20%22'2016-000000002'%22%7D -- from laserfiche coded

when that URL gets decoded (see website http://meyerweb.com/eric/tools/dencoder/ ) it looks like it does below…

http://coylaserweb/laserfiche/browse.aspx?repo=COY-Dev#?view=search&search={[Requisition]:[RequisitionNumber] ~= "'2016-000000002'"}

The decoded URL does not bring up the document when we paste it into a new browser window. We ran into this same issue with another customer and a laserfiche consultant applied a hotfix to the laserfiche software and this allowed the decoded URL to work. I have attached the email concerning all of the info related to this hotfix. Is this hotfix something that could be applied to Yonkers so that the decoded URLs will work? Please contact me with any questions.

0 0

Replies

replied on April 22, 2016

Hi Sandy,

Apologizes for the late reply. I can reproduce this behavior for decoded template search URLs in Web Access 10. Fortunately, in the soon to be released Web Access 10.1, the decoded search URL performs the search properly, even with the white space. Note that both Web Access 10.0 and 10.1 perform the search correctly with encoded URLs.

That being said, we generally recommend you keep URLs generated by Web Access encoded, and encode any URLs to Web Access you construct yourself. URL encoding helps ensure that the browser will parse URLs correctly, and that your URL won't include any reserved character that might confuse the browser. An example would be if your search syntax or field name included a '/'- the browser might interpret this as part of a path on the web server. While the encoding decreases readability, it will produce the most consistent results.

2 0

replied on April 27, 2016

Web Access 10.1 is now released and this fix is included.

0 0

You are not allowed to follow up in this post.

Question

Question

Web Access - problems with URLs that contain spaces.

Replies

Sign in to reply to this post.