[JIRA] Commented: (SNOW-134) Second Life Viewer Proxy Settings Are Ignored

Kadah Coba (JIRA) no-reply at lindenlab.cascadeo.com
Sat Jan 2 23:44:01 PST 2010


    [ http://jira.secondlife.com/browse/SNOW-134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=156423#action_156423 ] 

Kadah Coba commented on SNOW-134:
---------------------------------

I agree with Phillip. There are some performance issues with the current caching system anyway. Would also be nice to have the option to use an external, and common to many local client, caching squid proxy.

> Second Life Viewer Proxy Settings Are Ignored
> ---------------------------------------------
>
>                 Key: SNOW-134
>                 URL: http://jira.secondlife.com/browse/SNOW-134
>             Project: 6. Second Life Snowglobe - SNOW
>          Issue Type: Bug
>          Components: Performance 
>    Affects Versions: Snowglobe 1.0
>         Environment: OS: Mac OS X v10.5.7
> Viewer: Snowglobe v1.0.2 Release
> Proxy: Squid v3.0 STABLE16
>            Reporter: Forbin Fallen
>            Priority: Major
>             Fix For: Snowglobe 1.3
>
>
> Simply put, I use a personal Squid cache to cache, optimize, and speed-up every type of HTTP operation I have at home.  Unfortunately, clients such as Mozilla Firefox, the Second Life viewer, etc. simply weren't designed to utilize large cache sizes(i.e. I have an 8GB web cache setup...it's SO fast).
> Recently, just to see how HTTP texture processing was going, I enabled Squid's access logging(this essentially shows me what's going through the cache).
> I was amazed, surprised, and disappointed to see that the Second Life viewer(Snowglobe) honors the Web | Web Proxy setting for login...and that's all.  Even the built-in Net Radio support doesn't honor the proxy.  They're all direct connects!  Dang.
> This from my Squid log:
> 1248297048.690   3728 127.0.0.1 TCP_MISS/200 16670 CONNECT login.agni.lindenlab.com:443 - DIRECT/216.82.8.42 -
> I've no idea if Snowglobe is the appropriate place to file this bug, but I wanted to put it somewhere.
> Fixing this functionality could provide an orders of magnitute speed improvement for myself personally, as well as any/all corporate customers who run others proxies(i.e. MS Proxy Server, things like that).  Let me know if there's more detail I can provide to get this fixed.  Thanks!

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.secondlife.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


More information about the Jira-notify mailing list