Weblink 11-302 Errors when trying to test Custom Searches

asked on August 26, 2022

Hello,

Customer has a fresh install of WL11 (New LF Customer).

They have built some custom search that when launched should allow the user to search by Field.

When they click on one of the custom links from the Weblink welcome page, nothing happens.

We ran a network trace and are seeing a bunch of 302 Errors:

GET /WebLink/CustomSearch.aspx

302 0 0 21

302 0 0 15

302 0 0 10

302 0 0 5

Customer created a search that just browse a folder and that one works.

Customer is authenticating with LFDS.

Weblink is on the same server as LFDS.

I am not sure if this is related but I saw the following LF Answer Post regarding search results and the this bug was posted in response- ( weblink bug 357769.)

https://answers.laserfiche.com/questions/200039/weblink-11-doesnt-refresh-search-results#200796

Appreciate the feedback,

Jeff Curtis

0 0

replied on August 29, 2022

Where are these requests being redirected to? It will show in the "location" header in the response, in the network tab of the browser.

0 0

replied on August 29, 2022

Hey Brian,

I was just about to open an LF Support case for this.

Below is the request, from the HAR trace, that throws the 302 (Removed customer's Server.Domain and Repo name from the URL):

Request URL: https://CustomerServerName.Doamain.com/WebLink/CustomSearch.aspx?SearchName=APSearchbyInvoiceNumber&dbid=0&repo=CustomerRepo
Request Method: GET
Status Code: 302
Remote Address: :80

In the IIS Logs were are seeing the following:

2022-08-26 20:41:42 10.1.10.75 GET /WebLink/CustomSearch.aspx SearchName=APSearchbyInvoiceNumber&dbid=0&repo=CustomersRepor 443 BMAD\svc_laserfiche 10.1.10.75 Mozilla/5.0+(Windows+NT+10.0;+Win64;+x64)+AppleWebKit/537.36+(KHTML,+like+Gecko)+Chrome/104.0.0.0+Safari/537.36 https://CustomerServerName.Doamain.com/WebLink/Welcome.aspx?repo=BM-QA&dbid=0 302 0 0

Appreciate the feedback,

Jeff Curtis

0 0

replied on August 29, 2022

A support case is a good idea. The har trace will contain information about where the browser was redirected to, which is an important part. Presumably it's being sent to LFDS for (re-)authentication, but that's something to confirm. Then the question is why: if the session has really expired, or if it's due to some configuration problem.

0 0

Question

Question

Weblink 11-302 Errors when trying to test Custom Searches

Replies

Sign in to reply to this post.