I would say Lemmy issue. This is probably a default 502 internal sever error response (which I’ve been getting repeatedly from lemmy.world). Jerboa (I don’t use it btw) is only trying to parse the expected json response.
Yes the app could handle the error more gracefully but if Lemmy didn’t respond with an error jerboa wouldn’t need to.
personally I’d say it’s a Jerboa thing. the app should retry loading because sometimes I refresh after this happening and it immediately loads the proper content.
with all the different instances this sort of thing has to be kept in mind
Just retry is usually a bad ideia, specially that this problem is probably an overload, just adding retries can makes the problem.even worse with the app ddosing the server
The server responded with an appropriate HTTP status code and an appropriate MIME type. If the JSON were malformed I’d agree that this is a client issue, but in this case the client failed to deal with the error states of the underlying transport correctly. It shouldn’t have even tried to parse text/html as application/json in the first place!
I would say Lemmy issue. This is probably a default 502 internal sever error response (which I’ve been getting repeatedly from lemmy.world). Jerboa (I don’t use it btw) is only trying to parse the expected json response. Yes the app could handle the error more gracefully but if Lemmy didn’t respond with an error jerboa wouldn’t need to.
personally I’d say it’s a Jerboa thing. the app should retry loading because sometimes I refresh after this happening and it immediately loads the proper content.
with all the different instances this sort of thing has to be kept in mind
Just retry is usually a bad ideia, specially that this problem is probably an overload, just adding retries can makes the problem.even worse with the app ddosing the server
The server responded with an appropriate HTTP status code and an appropriate MIME type. If the JSON were malformed I’d agree that this is a client issue, but in this case the client failed to deal with the error states of the underlying transport correctly. It shouldn’t have even tried to parse text/html as application/json in the first place!
Yeah this makes more sense than my original comment