Update gemini query string support #107
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#107
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
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?
Blocked until verdict is reached on behavior by gemini working group
Presently any input request over gemini will wipe out the query string add a
?
to the end of the path and put the new input data. The spec if not clear on how this should work and I am working on a project where it would be better if any query string data was left there and any new query string data was appended via an&
. I'll check in with the mailing list before moving forward with this, but it is something to think about for the future.Fix gemini query string supportto Update gemini query string supportThis issue seems to be dropped, or at least not a current point of discussion. I believe Bombadillo is following the correct bahvior in replacing the query string fully when a query is submitted. Closing the issue.