Tag List Report

The following document contains the listing of user tags found in the code. Below is the summary of the occurrences per tag.

Tag ClassTotal number of occurrencesTag strings used by tag class
IDEA0IDEA
MUDO0MUDO
TODO66TODO
idea0idea
mudo0mudo
todo0todo

Each tag is detailed below:

TODO

Number of occurrences found in the code: 66

org.littleshoot.proxy.ChannelAdapterLine
Auto-generated method stub16
Auto-generated method stub21
Auto-generated method stub26
Auto-generated method stub31
Auto-generated method stub36
Auto-generated method stub45
Auto-generated method stub50
Auto-generated method stub55
Auto-generated method stub60
Auto-generated method stub65
Auto-generated method stub70
Auto-generated method stub75
Auto-generated method stub80
Auto-generated method stub85
Auto-generated method stub90
Auto-generated method stub95
Auto-generated method stub100
Auto-generated method stub105
Auto-generated method stub110
Auto-generated method stub115
Auto-generated method stub124
Auto-generated method stub129
org.littleshoot.proxy.ChannelFutureAdapterLine
Auto-generated method stub12
Auto-generated method stub17
Auto-generated method stub22
Auto-generated method stub28
Auto-generated method stub33
Auto-generated method stub38
Auto-generated method stub43
Auto-generated method stub48
Auto-generated method stub53
Auto-generated method stub58
Auto-generated method stub63
Auto-generated method stub68
Auto-generated method stub73
Auto-generated method stub78
Auto-generated method stub83
Auto-generated method stub88
Auto-generated method stub93
org.littleshoot.proxy.DefaultProxyCacheManagerLine
Return a 206 partial response with whatever data we have.87
org.littleshoot.proxy.HttpRelayingHandlerLine
I'm a little unclear as to when the request queue would ever actually be empty, but it is from time to time in practice. We've seen this particularly when behind proxies that govern access control on local networks, likely related to redirects.131
org.littleshoot.proxy.HttpRequestHandlerLine
We should really only allow access on 443, but this breaks what a lot of browsers do in practice. if (port != 443) {286
Set this back to readable true?312
org.littleshoot.proxy.HttpRequestUriRuleTestLine
Auto-generated method stub28
Auto-generated method stub37
Auto-generated method stub42
Auto-generated method stub47
Auto-generated method stub52
Auto-generated method stub57
Auto-generated method stub62
Auto-generated method stub67
Auto-generated method stub72
Auto-generated method stub77
Auto-generated method stub82
Auto-generated method stub87
Auto-generated method stub92
Auto-generated method stub97
Auto-generated method stub102
Auto-generated method stub107
Auto-generated method stub112
Auto-generated method stub117
Auto-generated method stub122
Auto-generated method stub127
Auto-generated method stub132
Auto-generated method stub137
org.littleshoot.proxy.ProxyUtilsLine
We don't append http:// or https:// here. Is it really OK to ignore the protocol?144