I have tried several times to duplicate the missing host name problem and cannot. We run ATS as a forward transparent proxy in production and in test and our logs look fine.
1303281687.404 901 172.28.56.102 TCP_MISS/206 821811 GET http://au.download.windowsupdate.com/msdownload/update/software/secu/2011/03/vcredist_x64_b19211187caa726619fefd80f199bf7df3266bb7.exe - DIRECT/au.download.windowsupdate.com application/octet-stream - 1303281688.458 836 172.28.56.102 TCP_MISS/206 806025 GET http://au.download.windowsupdate.com/msdownload/update/software/secu/2011/03/vcredist_x64_b19211187caa726619fefd80f199bf7df3266bb7.exe - DIRECT/au.download.windowsupdate.com application/octet-stream - This was a problem at one point and was fixed by 2.1.6. Are you doing any URL remapping? As for the use of the host name instead of the IP address in explicit forward proxy, I'll have to look at that. Is what you are seeing different from expected ATS behavior, or just different from squid? Tuesday, April 19, 2011, 12:56:40 AM, you wrote: > Hi Leif, > 2.1.7 still has bug with log. Forward transparent proxy. Wrong > hostname/URL/IP addr. > # traffic_logcat -f /opt/traffic/var/log/trafficserver/squid.blog > 1303191495.560 376 192.168.1.9 TCP_MISS/200 8599 GET > http:///docs/_static/basic.css - DIRECT/flask.pocoo.org text/css - > 1303191562.795 388 192.168.1.9 TCP_MISS/200 19803 GET > http:///community/graphics/campaigns/city.jpg - DIRECT/my.opera.com > image/jpeg - > Normal squid log looks like: > 1291725425.084 544 192.168.1.9 TCP_MISS/302 764 GET > http://www.google.ru/search? - DIRECT/74.125.232.16 text/html > In explicit proxy mode, ATS log is better but still wrong - instead of IP > address there is hostname: > 1303192346.438 125 192.168.1.9 TCP_IMS_MISS/304 270 GET > http://www.google.ru/images/srpr/nav_logo39.png - DIRECT/www.google.ru - - > I am reporting this bug 4th time! It is even not in issue list for 2.1.8. > Alexey. > On Sat, 16 Apr 2011 20:22:32 -0600, Leif Hedstrom <zw...@apache.org> wrote: >> Hi all, >> can you all please take a look at the open bug list for v2.1.8, and do >> one of the following (if you have an interest in one of several of the >> bugs): >> 1) If a bug is no longer needed for v2.1.8 (or the final v3.0 release), >> move it out to a v3.1 target. >> 2) If a bug is no longer reproducible, or invalid (or won't reproduce), >> please close it as "invalid" or "wontfix". >> 3) If a bug has high importance, comment on it, and we'll prioritize the >> remaining bugs. >> 4) If you have any more details on a bug, please add that. There are a >> few bugs that are lacking details, making them virtually impossible to >> fix / debug. >> We really need to get a v2.1.8 release out as soon as possible, so we >> can get a v3.0 release out in the April - May timeframe as we had planned. >> Thanks, >> -- leif
