60f48b1a3b
## Issue Due the `parseUri` not being used in a try-catch block, the thrown error surfaces all the way up and the 500 catch-all status was used. The search console was been complaining about this for a while now. I've always thought "what's the problem here, you entered the wrong claim format", but now I realized it's about the error code. ## Change `try-catch` the call as normal for that function, and return 404. We will still relay the error message it was. |
||
---|---|---|
.. | ||
component | ||
effects | ||
middleware | ||
page | ||
setup | ||
src | ||
static/pwa | ||
stubs | ||
bundle-id.js | ||
index.js | ||
lbry.js | ||
package.json | ||
webpack.config.js | ||
webpack.sw.config.js | ||
yarn.lock |