Handle HTTP error codes #1

Closed
opened 2 years ago by kj7rrv · 0 comments
kj7rrv commented 2 years ago
Owner

Currently, netrun treats any HTTP response as a script, whether the response code is 200, 404, 500, 418, or anything else; this means it will ask you if you want to run error pages as scripts. It won't try to run the pages (unless you tell it to), but it will show the content in less. It should only run the script with a 200, prompt the user for a redirect, and fail otherwise.

Currently, netrun treats any HTTP response as a script, whether the response code is 200, 404, 500, 418, or anything else; this means it will ask you if you want to run error pages as scripts. It won't try to run the pages (unless you tell it to), but it will show the content in `less`. It should only run the script with a 200, prompt the user for a redirect, and fail otherwise.
kj7rrv added the
bug
label 2 years ago
kj7rrv referenced this issue from a commit 2 years ago
kj7rrv closed this issue 2 years ago
Sign in to join this conversation.
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date

No due date set.

Dependencies

This issue currently doesn't have any dependencies.

Loading…
There is no content yet.