electricdusk/rushlink
3
3
Fork 3
Code Issues 21 Pull Requests 2 Releases Activity

"Bad accept-params" #17

New Issue
Closed
opened 2019-11-29 18:40:15 +01:00 by mrngm · 2 comments
mrngm commented 2019-11-29 18:40:15 +01:00
Collaborator
Copy Link
Nov 22 02:49:04 koulourakia rushlink[15035]: 2019/11/22 02:49:04 http: superfluous response.WriteHeader call from gitea.hashru.nl/dsprenkels/rushlink.render (views.go:121)
Nov 22 02:49:04 koulourakia rushlink[15035]: 2019/11/22 02:49:04 error: bad accept-params ("v=b3")
Nov 22 02:49:04 koulourakia rushlink[15035]: 2019/11/22 02:49:04 http: superfluous response.WriteHeader call from gitea.hashru.nl/dsprenkels/rushlink.renderError (views.go:131)
Nov 22 02:49:04 koulourakia rushlink[15035]: 2019/11/22 02:49:04 http: superfluous response.WriteHeader call from gitea.hashru.nl/dsprenkels/rushlink.render (views.go:82)
Nov 22 02:49:04 koulourakia rushlink[15035]: 2019/11/22 02:49:04 http: superfluous response.WriteHeader call from gitea.hashru.nl/dsprenkels/rushlink.render (views.go:121)
Nov 22 02:49:04 koulourakia rushlink[15035]: 2019/11/22 02:49:04 error: panic while recovering from another panic: bad accept-params ("v=b3")
``` Nov 22 02:49:04 koulourakia rushlink[15035]: 2019/11/22 02:49:04 http: superfluous response.WriteHeader call from gitea.hashru.nl/dsprenkels/rushlink.render (views.go:121) Nov 22 02:49:04 koulourakia rushlink[15035]: 2019/11/22 02:49:04 error: bad accept-params ("v=b3") Nov 22 02:49:04 koulourakia rushlink[15035]: 2019/11/22 02:49:04 http: superfluous response.WriteHeader call from gitea.hashru.nl/dsprenkels/rushlink.renderError (views.go:131) Nov 22 02:49:04 koulourakia rushlink[15035]: 2019/11/22 02:49:04 http: superfluous response.WriteHeader call from gitea.hashru.nl/dsprenkels/rushlink.render (views.go:82) Nov 22 02:49:04 koulourakia rushlink[15035]: 2019/11/22 02:49:04 http: superfluous response.WriteHeader call from gitea.hashru.nl/dsprenkels/rushlink.render (views.go:121) Nov 22 02:49:04 koulourakia rushlink[15035]: 2019/11/22 02:49:04 error: panic while recovering from another panic: bad accept-params ("v=b3") ```
mrngm commented 2019-11-29 20:44:01 +01:00
Author
Collaborator
Copy Link

Accept-header from Chromium:

accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,image/apng,*/*;q=0.8,application/signed-exchange;v=b3```
Accept-header from Chromium: ``` accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,image/apng,*/*;q=0.8,application/signed-exchange;v=b3```
mrngm closed this issue 2019-11-29 20:49:26 +01:00
electricdusk commented 2019-12-03 15:33:01 +01:00
Owner
Copy Link

Reopening, because this issue desperately needs a proper unit test.

Reopening, because this issue desperately needs a proper unit test.
electricdusk added the needs-test label 2019-12-03 15:33:38 +01:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
Uninteded behaviour
 feature
Request for a feature to be implemented
 good-beginner-bug
Bugs are probably easy to fix
 needs-test
Needs a regression test
 question
Question about the software
 wontfix
Wont be resolved
No Label needs-test
Milestone
No items
No Milestone
Assignees
Clear assignees
mara minnozz mrngm electricdusk
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: electricdusk/rushlink#17
Delete Branch "%!s()"

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?