8518
74%
master: 37%

Ran 23 Aug 2018 11:58PM UTC

Jobs 1

Files 269

Run time 42s

Badge

Embed ▾

pending completion

Build # 8518

Build Type

Pull #2910

travis-ci

Committed by

web-flow

Commit Message

gopher: Do not translate `?' to `%09'

Since GOPHER support was added in curl `?' character was automatically
translated to `%09' (`\t').
However, this behaviour does not seems documented in RFC 4266 and for
search selectors it is documented to directly use `%09' in the URL.
Apart that several gopher servers in the current gopherspace have
CGI support where `?' is used as part of the selector and translating
it to `%09' often leads to surprising results.

Pull Request Pull Request #2910: Do not translate `?' to `%09' for GOPHER

Run Details

20736 of 27936 relevant lines covered (74.23%)

605972.3 hits per line

Uncovered Existing Lines

Lines	Coverage	∆	File
1	85.86	-0.25%	lib/easy.c
2	86.31	-0.32%	lib/smtp.c
2	95.04	-1.65%	lib/curl_ntlm_core.c
13	68.47	-11.71%	lib/splay.c

Jobs

ID	Job ID	Ran	Files	Coverage
21	8518.21 (T=coverage)	23 Aug 2018 11:58PM UTC	269	74.23	Travis Job 8518.21

curl / curl / 8518
74%
master: 37%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Uncovered Existing Lines

Jobs

Source Files on build 8518

curl / curl / 8518 74% master: 37%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Uncovered Existing Lines

Jobs

Source Files on build 8518

curl / curl / 8518
74%
master: 37%

README BADGES
x