Search does not work well

[dschrempf]

Hi!

For a few weeks now, I have the following (weird) problem:

Hackage search and clicking the "Advanced options" button:

• Works fine with Chromium.
• Does not work at all with Qutebrowser.
• With Firefox, and when the ?terms= inquiry is left empty (which is the default when clicking "Search" on the top row), it takes around 10 seconds until the table is rendered and the "Advanced options" becomes responsive.

Does anybody else experience problems with Hackage search?

[gbaz]

With a new hackage redeploy (soon, I promise!) the responsiveness should be fixed: #1049

qutebrowser will be fixed by: #1062

[gbaz]

ok, redeploy done.

[MichelBoucey]

At the moment search requests are still broken.

https://hackage.haskell.org/packages/search?terms=lens`

gives :

Error with Hackage server: Unexpected content-type: For this resource the content-type was expected to be application/json, rather than multipart/form-data; boundary=---------------------------55663260525875955564249068061

[andreasabel]

I don't get this error.

[noughtmare]

If I open e.g. https://hackage.haskell.org/packages/search?terms=lens with Firefox I get this message in red:

Error with Hackage server: Unexpected content-type: For this resource the content-type was expected to be application/json, rather than multipart/form-data; boundary=---------------------------363225731826631620603428404

Edge gives a similar message:

[dschrempf]

On Qutebrowser and Firefox, search works for me now! I don't get any error messages. Thank you!

[tfausak]

Search is also broken for me. I've tried Firefox, Chrome, and Edge on Windows 10. I've also tried Safari on iOS 15.4.

[tfausak]

It seems to be working now for me.

[gbaz]

When we redeployed the server, we needed to force fastly to purge the cached search script in favor of the new one. Apologies for not realizing this after the deploy. Should now be resolved for everyone.

[gbaz]

Closing as the redeploy should have improved the above linked issues as well.

[gbaz]

(a hard refresh of the page to clear the cache may be necessary for end-users as well, sorry!)