Fixes querystring chaining issue #159
No reviewers
Labels
No Label
blocked
bug
build
documentation
duplicate
enhancement
finger
gemini
gopher
help wanted
http
in progress
invalid
local
needs-info
non-code
non-functional
non-urgent
question
release
rendering
suggestion
telnet
terminal
urgent
wontfix
No Milestone
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: sloum/bombadillo#159
Loading…
Reference in New Issue
No description provided.
Delete Branch "querystring"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This solves an issue brought up in #157
In short: if a query was followed by another query, rather than replacing the query element (
or
?
for gophr and gemini respectively) another was just getting tacked on to the end. THis has been resolved and the prior query element is removed.There was also a request to escape querystrings before sending to gemini servers. I implemented this but found that none of the search engines worked this way. A look at the spec does not make it clear what the expected behavior is. I am leaving out the querystring escaping for now so that users do not lose the ability to search.