Skip to content

Commit 2fdce0e

Browse files
committed
Simplify/shorten some of the error header messages
1 parent aa2204e commit 2fdce0e

File tree

1 file changed

+9
-11
lines changed

1 file changed

+9
-11
lines changed

src/components/view/http/http-error-header.tsx

Lines changed: 9 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -357,33 +357,31 @@ export const HttpErrorHeader = (p: {
357357
</HeaderText>
358358
: p.type === 'connection-refused'
359359
? <HeaderText>
360-
This typically means the server isn't running right now on the port you're using,
361-
although it's possible this is an intermittent connection issue. You can either
362-
try again, or you can mock requests like this to avoid sending them upstream
363-
at all.
360+
This typically means the server isn't running on the port you're using, though
361+
it is possible this is an intermittent connection issue. You can either try
362+
again, or mock requests like this to avoid sending them upstream at all.
364363
</HeaderText>
365364
: p.type === 'connection-reset'
366365
? <HeaderText>
367-
This could be due to a connection issue, or may be caused by an issue on the server.
368-
In many cases, this is an intermittent issue that will be solved by retrying
369-
the request. You can also mock requests like this, to avoid sending them upstream
370-
at all.
366+
This could be due to a connection issue, or an issue with the server.
367+
This may be an intermittent issue that will be solved by retrying the request, or
368+
you can mock requests like this to avoid sending them upstream at all.
371369
</HeaderText>
372370
: p.type === 'client-abort'
373371
? <HeaderText>
374-
This could be due to connection issues, general problems in the client, or that
372+
This could be due to connection issues, problems within the client, or that
375373
the client simply no longer wanted to receive the response and closed the
376374
connection intentionally.
377375
</HeaderText>
378376
: p.type === 'client-timeout'
379377
? <HeaderText>
380-
This could be due to connection issues, general problems in the client, or delays
378+
This could be due to connection issues, problems within the client, or delays
381379
generating the complete body of the request. This might be resolved by retrying
382380
the request, or sending a simpler request with a smaller or easier to generate body.
383381
</HeaderText>
384382
: p.type === 'server-timeout'
385383
? <HeaderText>
386-
This could be due to connection issues, general issues on the server, or issues
384+
This could be due to connection issues, problems within the server, or issues
387385
with handling this request specifically. This might be resolved by retrying
388386
the request, or you can mock requests like this to avoid sending them upstream
389387
at all.

0 commit comments

Comments
 (0)