[squid-users] URL too large??

Tue Dec 13 20:38:14 UTC 2016

Yes.

Let's cut discussion. Answer to op, not for me. If you have to tell some.

14.12.2016 2:28, Eliezer Croitoru пишет:
> And you are still using squid?
>
> Eliezer
>
> ----
> Eliezer Croitoru
> Linux System Administrator
> Mobile: +972-5-28704261
> Email: eliezer at ngtech.co.il
>
>
> -----Original Message-----
> From: Yuri Voinov [mailto:yvoinov at gmail.com] 
> Sent: Tuesday, December 13, 2016 10:09 PM
> To: Eliezer Croitoru <eliezer at ngtech.co.il>; squid-users at lists.squid-cache.org
> Subject: Re: [squid-users] URL too large??
>
> 14.12.2016 2:05, Eliezer Croitoru пишет:
>> Hey Yuri,
>>
>> It's not right that the Internet is 4*8K in the urls.
>> It's just that it happens that some of the Internet users abuse their options to enter something in the browser.
>> Most browsers doesn't support more then 16k and the number which was mentioned was 100K++ so it's either not HTTP or something else.
> I don't care. I know all about this problem and solve it years ago.
>> If you are managing a network like a soho this is a very nice restriction to have 8k or 16k and in some cases 24k limit for a url maximum size.
>> The defaults are defaults but depends on the applications which are being used the choice of the defaults or special compiled version would change.
> Please, stop lecture me. I have big enough networks, I'm solve this problem years ago, I know exactly which URL_MAX satisfied my requirements, I'm builds all critical software from sources, I know how to change defaults and what are they means.
>
> Thank you.
>> Eliezer
>> ----
>> http://ngtech.co.il/lmgtfy/
>> Linux System Administrator
>> Mobile: +972-5-28704261
>> Email: eliezer at ngtech.co.il
>>
>>
>> From: squid-users [mailto:squid-users-bounces at lists.squid-cache.org] 
>> On Behalf Of Yuri Voinov
>> Sent: Tuesday, December 13, 2016 9:46 PM
>> To: squid-users at lists.squid-cache.org
>> Subject: Re: [squid-users] URL too large??
>>
>> It means exactly what it said: URL too long.
>> In Squid's defaults set 8k for URL size. This was reasonable maximum 10 years ago.
>> Now it seems too small (at least 4 times) because of now Internet full of adware bullshit (referrals/trackers/counters etc.) which is often more 8k.
>> You can easy fix it (if you worry about it. It seems for end-user like hang/broken links) if you build squid from source. Just change vaule MAX_URL in src/defines.h and recompile.
>> But if you do this, beware - some things become slower, and danger of deinal of service exists.
>> That's it.
>> WBR, Yuri
>>
>> 14.12.2016 1:05, Odhiambo Washington пишет:
>> I did not dig deep into it I couldn't scan the access log for it because I had no idea what 'too long' meant. 
>> I will ignore it until someone says they're unable to access a website, and they can give me details of what it is.
>>
>>
>> On 13 December 2016 at 19:51, Eliezer Croitoru <mailto:eliezer at ngtech.co.il> wrote:
>> I think that the maximum size was 64k and it's way above this. 
>> It should not be an issue if this is some weird application creating some random url which doesn't have meaning.
>> But if you know what is creating such a url it's a whole another story.
>> Can you reproduce\recreate this url?
>>
>> Eliezer
>>
>> ----
>> Eliezer Croitoru
>> Linux System Administrator
>> Mobile+WhatsApp: +972-5-28704261
>> Email: mailto:eliezer at ngtech.co.il
>>
>>
>> On Tue, Dec 13, 2016 at 11:08 AM, Odhiambo Washington <mailto:odhiambo at gmail.com> wrote:
>> Hi,
>>
>> Saw this on my cache.log (squid-3.5.22, FreeBSD-9.3,):
>>
>> 2016/12/13 11:47:55| WARNING: no_suid: setuid(0): (1) Operation not 
>> permitted
>> 2016/12/13 11:47:55| WARNING: no_suid: setuid(0): (1) Operation not 
>> permitted
>> 2016/12/13 11:47:55| HTCP Disabled.
>> 2016/12/13 11:47:55| Finished loading MIME types and icons.
>> 2016/12/13 11:47:55| Accepting NAT intercepted HTTP Socket connections 
>> at local=[::]:13128 remote=[::] FD 39 flags=41
>> 2016/12/13 11:47:55| Accepting HTTP Socket connections at 
>> local=[::]:13130 remote=[::] FD 40 flags=9
>> 2016/12/13 11:47:55| Accepting NAT intercepted SSL bumped HTTPS Socket 
>> connections at local=[::]:13129 remote=[::] FD 41 flags=41
>> 2016/12/13 11:47:55| Accepting ICP messages on [::]:3130
>> 2016/12/13 11:47:55| Sending ICP messages from [::]:3130
>> 2016/12/13 11:53:25| urlParse: URL too large (11654 bytes)
>>
>>
> --
> Cats - delicious. You just do not know how to cook them.
>

-- 
Cats - delicious. You just do not know how to cook them.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0x613DEC46.asc
Type: application/pgp-keys
Size: 2437 bytes
Desc: not available
URL: <http://lists.squid-cache.org/pipermail/squid-users/attachments/20161214/990c4b02/attachment-0001.key>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: OpenPGP digital signature
URL: <http://lists.squid-cache.org/pipermail/squid-users/attachments/20161214/990c4b02/attachment-0001.sig>