BUG - ParseHttp exception. Recovering, but please report this: runtime error: slice bounds out of range #6409

anergiti · 2018-02-19T13:10:02Z

Hello,
Opening a bug issue per elasticteam request:

Hello.
im running packetbeat; Version: 6.2.1 on ubuntu machine,
Connected to Elasticsearch version 5.1.2.
capturing mirrored traffic.

this is my yml file:

`packetbeat.interfaces.device: eth5
packetbeat.interfaces.type: af_packet
packetbeat.interfaces.snaplen: 1500
packetbeat.interfaces.buffer_size_mb: 500
packetbeat.flows:
ports: [53]

include_authorities controls whether or not the dns.authorities field
(authority resource records) is added to messages.
include_authorities: true

include_additionals controls whether or not the dns.additionals field
(additional resource records) is added to messages.
include_additionals: true

type: http
Configure the ports where to listen for HTTP traffic. You can disable
the HTTP protocol by commenting out the list of ports.
enabled: true
ports: [80, 8080]
send_headers: false
send_all_headers: false
include_body_for: ["application/json"]
send_request: true
send_response: true
transaction_timeout: 20s
output.elasticsearch:

Array of hosts to connect to.
hosts: ["1.1.1.1:9200"]`

most of packets are not parsed due to ParseHttp exception - slice bounds out of range.

This is a snip of debug logs of Packetbeat:

2018-02-16T13:59:05.332-0500	INFO	instance/beat.go:468	Home path: [/usr/share/packetbeat/bin] Config path: [/usr/share/packetbeat/bin] Data path: [/usr/share/packetbeat/bin/data] Logs path: [/usr/share/packetbeat/bin/logs]
2018-02-16T13:59:05.335-0500	INFO	instance/beat.go:475	Beat UUID: 418b8929-9abc-4c5b-9c17-ff0e13fd876e
2018-02-16T13:59:05.335-0500	INFO	instance/beat.go:213	Setup Beat: packetbeat; Version: 6.2.1
2018-02-16T13:59:05.335-0500	INFO	elasticsearch/client.go:145	Elasticsearch url: http://myelasticserver:9200
2018-02-16T13:59:05.335-0500	INFO	pipeline/module.go:76	Beat name: server.name.fqdn
2018-02-16T13:59:05.336-0500	INFO	procs/procs.go:78	Process matching disabled
2018-02-16T13:59:05.340-0500	INFO	instance/beat.go:301	packetbeat start running.
2018-02-16T13:59:05.340-0500	INFO	[monitoring]	log/log.go:97	Starting metrics logging every 30s
2018-02-16T13:59:22.423-0500	ERROR	runtime/panic.go:35	ParseHttp exception. Recovering, but please report this: runtime error: slice bounds out of range.	{"stack": "github.com/elastic/beats/libbeat/logp.Recover\n\t/go/src/github.com/elastic/beats/libbeat/logp/global.go:88\nruntime.call32\n\t/usr/local/go/src/runtime/asm_amd64.s:509\nruntime.gopanic\n\t/usr/local/go/src/runtime/panic.go:491\nruntime.panicslice\n\t/usr/local/go/src/runtime/panic.go:35\ngithub.com/elastic/beats/packetbeat/protos/http.(*parser).parseHTTPLine\n\t/go/src/github.com/elastic/beats/packetbeat/protos/http/http_parser.go:179\ngithub.com/elastic/beats/packetbeat/protos/http.(*parser).parse\n\t/go/src/github.com/elastic/beats/packetbeat/protos/http/http_parser.go:107\ngithub.com/elastic/beats/packetbeat/protos/http.(*httpPlugin).doParse\n\t/go/src/github.com/elastic/beats/packetbeat/protos/http/http.go:293\ngithub.com/elastic/beats/packetbeat/protos/http.(*httpPlugin).Parse\n\t/go/src/github.com/elastic/beats/packetbeat/protos/http/http.go:224\ngithub.com/elastic/beats/packetbeat/protos/tcp.(*TCPStream).addPacket\n\t/go/src/github.com/elastic/beats/packetbeat/protos/tcp/tcp.go:115\ngithub.com/elastic/beats/packetbeat/protos/tcp.(*TCP).Process\n\t/go/src/github.com/elastic/beats/packetbeat/protos/tcp/tcp.go:208\ngithub.com/elastic/beats/packetbeat/decoder.(*Decoder).onTCP\n\t/go/src/github.com/elastic/beats/packetbeat/decoder/decoder.go:317\ngithub.com/elastic/beats/packetbeat/decoder.(*Decoder).process\n\t/go/src/github.com/elastic/beats/packetbeat/decoder/decoder.go:258\ngithub.com/elastic/beats/packetbeat/decoder.(*Decoder).OnPacket\n\t/go/src/github.com/elastic/beats/packetbeat/decoder/decoder.go:164\ngithub.com/elastic/beats/packetbeat/sniffer.(*Sniffer).Run\n\t/go/src/github.com/elastic/beats/packetbeat/sniffer/sniffer.go:193\ngithub.com/elastic/beats/packetbeat/beater.(*packetbeat).Run.func2\n\t/go/src/github.com/elastic/beats/packetbeat/beater/packetbeat.go:202"}
2018-02-16T13:59:35.342-0500	INFO	[monitoring]	log/log.go:124	Non-zero metrics in the last 30s {"monitoring": {"metrics": {"beat":{"cpu":{"system":{"ticks":10810,"time":10818},"total":{"ticks":58880,"time":58888,"value":58880},"user":{"ticks":48070,"time":48070}},"info":{"ephemeral_id":"a78c6431-fe65-4b55-9c43-624537eac328","uptime":{"ms":30015}},"memstats":{"gc_next":7913065664,"memory_alloc":5098753768,"memory_total":10229529576,"rss":6588616704}},"http":{"unmatched_responses":315004},"libbeat":{"config":{"module":{"running":0}},"output":{"type":"elasticsearch"},"pipeline":{"clients":12,"events":{"active":0}}},"system":{"cpu":{"cores":32},"load":{"1":1.83,"15":1.31,"5":1.57,"norm":{"1":0.0572,"15":0.0409,"5":0.0491}}},"tcp":{"dropped_because_of_gaps":14523}}}}
2018-02-16T14:00:05.342-0500	INFO	[monitoring]	log/log.go:124	Non-zero metrics in the last 30s {"monitoring": {"metrics": {"beat":{"cpu":{"system":{"ticks":18710,"time":18712},"total":{"ticks":105240,"time":105243,"value":105240},"user":{"ticks":86530,"time":86531}},"info":{"ephemeral_id":"a78c6431-fe65-4b55-9c43-624537eac328","uptime":{"ms":60014}},"memstats":{"gc_next":7542307872,"memory_alloc":7108923240,"memory_total":19867083776,"rss":2189402112}},"http":{"unmatched_responses":297639},"libbeat":{"config":{"module":{"running":0}},"pipeline":{"clients":12,"events":{"active":0}}},"system":{"load":{"1":2.12,"15":1.35,"5":1.66,"norm":{"1":0.0663,"15":0.0422,"5":0.0519}}},"tcp":{"dropped_because_of_gaps":18712}}}}
2018-02-16T14:00:15.803-0500	INFO	beater/packetbeat.go:221	Packetbeat send stop signal
2018-02-16T14:00:15.884-0500	INFO	instance/beat.go:308	packetbeat stopped.
2018-02-16T14:00:15.885-0500	INFO	[monitoring]	log/log.go:132	Total non-zero metrics	{"monitoring": {"metrics": {"beat":{"cpu":{"system":{"ticks":22060,"time":22065},"total":{"ticks":130490,"time":130496,"value":130490},"user":{"ticks":108430,"time":108431}},"info":{"ephemeral_id":"a78c6431-fe65-4b55-9c43-624537eac328","uptime":{"ms":70557}},"memstats":{"gc_next":7383853248,"memory_alloc":4384858264,"memory_total":23284031896,"rss":8257155072}},"http":{"unmatched_responses":716837},"libbeat":{"config":{"module":{"running":0}},"output":{"type":"elasticsearch"},"pipeline":{"clients":12,"events":{"active":0}}},"system":{"cpu":{"cores":32},"load":{"1":2.24,"15":1.37,"5":1.7,"norm":{"1":0.07,"15":0.0428,"5":0.0531}}},"tcp":{"dropped_because_of_gaps":39174}}}}
2018-02-16T14:00:15.885-0500	INFO	[monitoring]	log/log.go:133	Uptime: 1m10.558590286s
2018-02-16T14:00:15.885-0500	INFO	[monitoring]	log/log.go:110	Stopping metrics logging.

The text was updated successfully, but these errors were encountered:

andrewkroh · 2018-02-20T21:31:53Z

Based on the stack trace it looks like a slice indexing bug while attempting to parse the HTTP header. @anergiti Would you be able to capture a short trace and attach it here so we can replay the data through Packetbeat?

runtime.panicslice
	/usr/local/go/src/runtime/panic.go:35
github.com/elastic/beats/packetbeat/protos/http.(*parser).parseHTTPLine
	/go/src/github.com/elastic/beats/packetbeat/protos/http/http_parser.go:179
github.com/elastic/beats/packetbeat/protos/http.(*parser).parse
	/go/src/github.com/elastic/beats/packetbeat/protos/http/http_parser.go:107
github.com/elastic/beats/packetbeat/protos/http.(*httpPlugin).doParse
	/go/src/github.com/elastic/beats/packetbeat/protos/http/http.go:293
github.com/elastic/beats/packetbeat/protos/http.(*httpPlugin).Parse
	/go/src/github.com/elastic/beats/packetbeat/protos/http/http.go:224
github.com/elastic/beats/packetbeat/protos/tcp.(*TCPStream).addPacket
	/go/src/github.com/elastic/beats/packetbeat/protos/tcp/tcp.go:115
github.com/elastic/beats/packetbeat/protos/tcp.(*TCP).Process
	/go/src/github.com/elastic/beats/packetbeat/protos/tcp/tcp.go:208
github.com/elastic/beats/packetbeat/decoder.(*Decoder).onTCP
	/go/src/github.com/elastic/beats/packetbeat/decoder/decoder.go:317
github.com/elastic/beats/packetbeat/decoder.(*Decoder).process
	/go/src/github.com/elastic/beats/packetbeat/decoder/decoder.go:258
github.com/elastic/beats/packetbeat/decoder.(*Decoder).OnPacket
	/go/src/github.com/elastic/beats/packetbeat/decoder/decoder.go:164
github.com/elastic/beats/packetbeat/sniffer.(*Sniffer).Run
	/go/src/github.com/elastic/beats/packetbeat/sniffer/sniffer.go:193
github.com/elastic/beats/packetbeat/beater.(*packetbeat).Run.func2
	/go/src/github.com/elastic/beats/packetbeat/beater/packetbeat.go:202"

And this looks similar to #2150.

https://github.com/elastic/beats/blob/v6.2.1/packetbeat/protos/http/http_parser.go#L179

ph · 2018-02-20T22:33:19Z

This is indeed look similar to #2150, I know I played with that code a few month ago, a pcap dump would be very helpful.

On Tue, Feb 20, 2018 at 4:31 PM Andrew Kroh ***@***.***> wrote: Based on the stack trace it looks like a slice indexing bug while attempting to parse the HTTP header. @anergiti <https://github.com/anergiti> Would you be able to capture a short trace <https://www.elastic.co/guide/en/beats/packetbeat/current/recording-trace.html> and attach it here so we can replay the data through Packetbeat? runtime.panicslice /usr/local/go/src/runtime/panic.go:35github.com/elastic/beats/packetbeat/protos/http.(*parser).parseHTTPLine /go/src/github.com/elastic/beats/packetbeat/protos/http/http_parser.go:179github.com/elastic/beats/packetbeat/protos/http.(*parser).parse /go/src/github.com/elastic/beats/packetbeat/protos/http/http_parser.go:107github.com/elastic/beats/packetbeat/protos/http.(*httpPlugin).doParse /go/src/github.com/elastic/beats/packetbeat/protos/http/http.go:293github.com/elastic/beats/packetbeat/protos/http.(*httpPlugin).Parse /go/src/github.com/elastic/beats/packetbeat/protos/http/http.go:224github.com/elastic/beats/packetbeat/protos/tcp.(*TCPStream).addPacket /go/src/github.com/elastic/beats/packetbeat/protos/tcp/tcp.go:115github.com/elastic/beats/packetbeat/protos/tcp.(*TCP).Process /go/src/github.com/elastic/beats/packetbeat/protos/tcp/tcp.go:208github.com/elastic/beats/packetbeat/decoder.(*Decoder).onTCP /go/src/github.com/elastic/beats/packetbeat/decoder/decoder.go:317github.com/elastic/beats/packetbeat/decoder.(*Decoder).process /go/src/github.com/elastic/beats/packetbeat/decoder/decoder.go:258github.com/elastic/beats/packetbeat/decoder.(*Decoder).OnPacket /go/src/github.com/elastic/beats/packetbeat/decoder/decoder.go:164github.com/elastic/beats/packetbeat/sniffer.(*Sniffer).Run /go/src/github.com/elastic/beats/packetbeat/sniffer/sniffer.go:193github.com/elastic/beats/packetbeat/beater.(*packetbeat).Run.func2 /go/src/github.com/elastic/beats/packetbeat/beater/packetbeat.go:202" And this looks similar to #2150 <#2150>. https://github.com/elastic/beats/blob/v6.2.1/packetbeat/protos/http/http_parser.go#L179 — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#6409 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAACgFO-vc21zDjWQK5fxlnSB38qTW4Vks5tWznKgaJpZM4SKhhK> .

-- ph

anergiti · 2018-02-21T08:52:20Z

Hey @andrewkroh
Please see attached zipped pcap snip.
Thanks for helping here!

trace_summary.pcap.zip

andrewkroh · 2018-02-21T23:46:53Z

I wasn't able to open the attached pcap file (after unzipping) with Packetbeat or Wireshark. I think it got corrupted somehow. Not sure if it was during the upload or something Packetbeat did while writing it. Sorry to ask, but can you try again?

anergiti · 2018-02-22T15:22:22Z

Hey,
when trying to tail the file its seems as binary file. so its i dont think it`s corrupted.
tcpdump might help?

andrewkroh · 2018-02-22T15:30:43Z

pcap files are not plain text so it is expected that tail doesn't work properly.

-dump produces the same file type as tcpdump -w, so yes, you could try tcpdump. You just need to setup the BPF filter the same as Packetbeat (like tcp port 80 or tcp port 8080).

The files produced by -dump should also be readable by tcpdump -r [file.pcap]. So please try that before uploading. Thanks!

anergiti · 2018-02-22T15:45:03Z

mytrace.pcap.zip
hope this one good

adriansr · 2018-02-22T23:01:51Z

Hi @anergiti , can you confirm that you get the runtime error when running this pcap through packetbeat? Because I don't seem to get it.

Try with:

packetbeat run -e -I mytrace.pcap
please note that the -I argument is an uppercase i

anergiti · 2018-02-24T20:19:39Z

Yup you right.
i really dont get it.
while im running packetbeat with .pcap - all ok.
while running standalone (./packetbeat run -e -c /etc/packetbeat/packetbeat.yml) - lots of parsing errors.

is there a difference between pcap and standalone?

adriansr · 2018-02-28T22:05:13Z

@anergiti can you try capturing more traffic with the -dump option and make sure that you see the errors in the log?

anergiti · 2018-03-04T09:18:34Z

Sure, can try
cuz throughput is overwhelming.

anergiti · 2018-03-05T13:28:20Z

guys im really @ dead end here.
pcap file reaches hundreds of MB which cannot be uploaded here.
anyway,
while running
./packetbeat -e -c /etc/packetbeat/packetbeat.yml -dump trace.pcap
i see the parsing errors - attached scrn shot.

while running ./packetbeat run -e -I trace.pcap
NO ERROR AT ALL.

i will be happy to set remote session (skype, hangout) if that`s possible.
thanks.

anergiti · 2018-04-03T14:47:01Z

Hey. i have uploaded the pcap file. can download it from dropbox link bellow.
Thanks!

https://www.dropbox.com/s/3citcxi7ihiwmqw/trace.pcap?dl=0

There was a bounds check error in parsing HTTP responses. A malformed response line in the form "HTTP/1.1\r\n" would cause a panic when parsed.

There was a bounds check error in parsing HTTP responses. A malformed response line in the form "HTTP/1.1\r\n" would cause a panic when parsed. Related to #6409

There was a bounds check error in parsing HTTP responses. A malformed response line in the form "HTTP/1.1\r\n" would cause a panic when parsed. Related to elastic#6409

There was a bounds check error in parsing HTTP responses. A malformed response line in the form "HTTP/1.1\r\n" would cause a panic when parsed. Related to #6409

anergiti · 2018-04-15T08:04:02Z

hey guys,
Thanks for taking care of this.
do you have an expectation of a solution?
thanks!

anergiti · 2018-04-30T11:03:48Z

@andrewkroh how are you?
appreciate an update regarding this issue.
Thanks!

adriansr · 2018-04-30T15:25:36Z

Hi @anergiti,

A fix for this problem (#6750) was included in 6.2.4.

teotwaki · 2018-04-30T18:59:01Z

@adriansr I just updated to 6.2.4, but still see this issue in production. I'm trying to figure out how to provide a pcap without sensitive data.

adriansr · 2018-04-30T19:12:04Z

Can you provide the stacktrace reported by packetbeat?

teotwaki · 2018-04-30T20:14:59Z

github.com/elastic/beats/libbeat/logp.Recover
	/go/src/github.com/elastic/beats/libbeat/logp/global.go:88
runtime.call32
	/usr/local/go/src/runtime/asm_amd64.s:509
runtime.gopanic
	/usr/local/go/src/runtime/panic.go:491
runtime.panicslice
	/usr/local/go/src/runtime/panic.go:35
github.com/elastic/beats/packetbeat/protos/http.(*parser).parseHTTPLine
	/go/src/github.com/elastic/beats/packetbeat/protos/http/http_parser.go:179
github.com/elastic/beats/packetbeat/protos/http.(*parser).parse
	/go/src/github.com/elastic/beats/packetbeat/protos/http/http_parser.go:107
github.com/elastic/beats/packetbeat/protos/http.(*httpPlugin).doParse
	/go/src/github.com/elastic/beats/packetbeat/protos/http/http.go:293
github.com/elastic/beats/packetbeat/protos/http.(*httpPlugin).Parse
	/go/src/github.com/elastic/beats/packetbeat/protos/http/http.go:224
github.com/elastic/beats/packetbeat/protos/tcp.(*TCPStream).addPacket
	/go/src/github.com/elastic/beats/packetbeat/protos/tcp/tcp.go:115
github.com/elastic/beats/packetbeat/protos/tcp.(*TCP).Process
	/go/src/github.com/elastic/beats/packetbeat/protos/tcp/tcp.go:208
github.com/elastic/beats/packetbeat/decoder.(*Decoder).onTCP
	/go/src/github.com/elastic/beats/packetbeat/decoder/decoder.go:317
github.com/elastic/beats/packetbeat/decoder.(*Decoder).process
	/go/src/github.com/elastic/beats/packetbeat/decoder/decoder.go:258
github.com/elastic/beats/packetbeat/decoder.(*Decoder).OnPacket
	/go/src/github.com/elastic/beats/packetbeat/decoder/decoder.go:164
github.com/elastic/beats/packetbeat/sniffer.(*Sniffer).Run
	/go/src/github.com/elastic/beats/packetbeat/sniffer/sniffer.go:193
github.com/elastic/beats/packetbeat/beater.(*packetbeat).Run.func2
	/go/src/github.com/elastic/beats/packetbeat/beater/packetbeat.go:202

A broken HTTP request caused the parser to report a panic. Fixes elastic#6409

A broken HTTP request caused the parser to report a panic. Fixes #6409

A broken HTTP request caused the parser to report a panic. Fixes elastic#6409

A broken HTTP request caused the parser to report a panic. Fixes #6409

A broken HTTP request caused the parser to report a panic. Fixes elastic#6409 (cherry picked from commit a634802)

A broken HTTP request caused the parser to report a panic. Fixes #6409 (cherry picked from commit a634802)

…elastic#7339) A broken HTTP request caused the parser to report a panic. Fixes elastic#6409 (cherry picked from commit 73a009f)

There was a bounds check error in parsing HTTP responses. A malformed response line in the form "HTTP/1.1\r\n" would cause a panic when parsed. Related to elastic#6409

andrewkroh added bug Packetbeat labels Feb 20, 2018

adriansr added a commit to adriansr/beats that referenced this issue Apr 3, 2018

Fix minor panic in http parser (elastic#6409)

66a1a1d

There was a bounds check error in parsing HTTP responses. A malformed response line in the form "HTTP/1.1\r\n" would cause a panic when parsed.

adriansr mentioned this issue Apr 3, 2018

Fix minor panic in http parser #6750

Merged

andrewkroh pushed a commit that referenced this issue Apr 4, 2018

Fix minor panic in http parser (#6750)

1fb759c

There was a bounds check error in parsing HTTP responses. A malformed response line in the form "HTTP/1.1\r\n" would cause a panic when parsed. Related to #6409

andrewkroh pushed a commit that referenced this issue Apr 6, 2018

Fix minor panic in http parser (#6750)

6db64c6

There was a bounds check error in parsing HTTP responses. A malformed response line in the form "HTTP/1.1\r\n" would cause a panic when parsed. Related to #6409

andrewkroh pushed a commit that referenced this issue Apr 6, 2018

Fix minor panic in http parser (#6750)

12bcd55

There was a bounds check error in parsing HTTP responses. A malformed response line in the form "HTTP/1.1\r\n" would cause a panic when parsed. Related to #6409

adriansr closed this as completed Apr 30, 2018

adriansr reopened this Apr 30, 2018

adriansr mentioned this issue May 2, 2018

Fix out of bounds access in packetbeat's HTTP parser #6997

Merged

adriansr added a commit to adriansr/beats that referenced this issue May 2, 2018

Fix out of bounds access in HTTP parser (elastic#6409)

41c1553

A broken HTTP request caused the parser to report a panic. Fixes elastic#6409

ruflin closed this as completed in #6997 May 3, 2018

ruflin pushed a commit that referenced this issue May 3, 2018

Fix out of bounds access in HTTP parser (#6409) (#6997)

a634802

A broken HTTP request caused the parser to report a panic. Fixes #6409

adriansr added a commit to adriansr/beats that referenced this issue May 9, 2018

Fix out of bounds access in HTTP parser (elastic#6409) (elastic#6997)

966b38e

A broken HTTP request caused the parser to report a panic. Fixes elastic#6409

adriansr mentioned this issue May 9, 2018

5.6: Fix out of bounds access in HTTP parser #7065

Merged

andrewkroh pushed a commit that referenced this issue May 9, 2018

Fix out of bounds access in HTTP parser (#6409) (#6997) (#7065)

1b2b1d3

A broken HTTP request caused the parser to report a panic. Fixes #6409

adriansr mentioned this issue Jun 15, 2018

Cherry-pick #6997 to 6.3: Fix out of bounds access in packetbeat's HTTP parser #7339

Merged

adriansr added a commit to adriansr/beats that referenced this issue Jun 15, 2018

Fix out of bounds access in HTTP parser (elastic#6409) (elastic#6997)

ac77d8b

A broken HTTP request caused the parser to report a panic. Fixes elastic#6409 (cherry picked from commit a634802)

ruflin pushed a commit that referenced this issue Jun 15, 2018

Fix out of bounds access in HTTP parser (#6409) (#6997) (#7339)

49fbc32

A broken HTTP request caused the parser to report a panic. Fixes #6409 (cherry picked from commit a634802)

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

BUG - ParseHttp exception. Recovering, but please report this: runtime error: slice bounds out of range #6409

BUG - ParseHttp exception. Recovering, but please report this: runtime error: slice bounds out of range #6409

anergiti commented Feb 19, 2018 •

edited by andrewkroh

Loading

andrewkroh commented Feb 20, 2018

ph commented Feb 20, 2018 via email

anergiti commented Feb 21, 2018

andrewkroh commented Feb 21, 2018

anergiti commented Feb 22, 2018

andrewkroh commented Feb 22, 2018 •

edited

Loading

anergiti commented Feb 22, 2018

adriansr commented Feb 22, 2018

anergiti commented Feb 24, 2018

adriansr commented Feb 28, 2018

anergiti commented Mar 4, 2018

anergiti commented Mar 5, 2018

anergiti commented Apr 3, 2018

anergiti commented Apr 15, 2018

anergiti commented Apr 30, 2018

adriansr commented Apr 30, 2018 •

edited

Loading

teotwaki commented Apr 30, 2018

adriansr commented Apr 30, 2018 •

edited

Loading

teotwaki commented Apr 30, 2018

BUG - ParseHttp exception. Recovering, but please report this: runtime error: slice bounds out of range #6409

BUG - ParseHttp exception. Recovering, but please report this: runtime error: slice bounds out of range #6409

Comments

anergiti commented Feb 19, 2018 • edited by andrewkroh Loading

andrewkroh commented Feb 20, 2018

ph commented Feb 20, 2018 via email

anergiti commented Feb 21, 2018

andrewkroh commented Feb 21, 2018

anergiti commented Feb 22, 2018

andrewkroh commented Feb 22, 2018 • edited Loading

anergiti commented Feb 22, 2018

adriansr commented Feb 22, 2018

anergiti commented Feb 24, 2018

adriansr commented Feb 28, 2018

anergiti commented Mar 4, 2018

anergiti commented Mar 5, 2018

anergiti commented Apr 3, 2018

anergiti commented Apr 15, 2018

anergiti commented Apr 30, 2018

adriansr commented Apr 30, 2018 • edited Loading

teotwaki commented Apr 30, 2018

adriansr commented Apr 30, 2018 • edited Loading

teotwaki commented Apr 30, 2018

anergiti commented Feb 19, 2018 •

edited by andrewkroh

Loading

andrewkroh commented Feb 22, 2018 •

edited

Loading

adriansr commented Apr 30, 2018 •

edited

Loading

adriansr commented Apr 30, 2018 •

edited

Loading