Bug #3288

Configure forward_max_tries for Squid

Added by Jacob Oliver almost 4 years ago. Updated almost 4 years ago.

Status:CLOSEDStart date:
Priority:NormalDue date:
Assignee:-% Done:

100%

Category:nethserver-squid
Target version:v6.7
Security class: Resolution:
Affected version:v6.7 NEEDINFO:No

Description

There's an issue accessing Office 365 through Squid depending on the users location.

This is due to the way Microsoft load balance Office 365 (And deny access to certain IP's from different locations).

The default Squid value for "forward_max_tries" is 10 - This should be set to 25 in order to allow Office 365 to work with a NethServer proxy worldwide.

Adding the following line to /etc/squid/squid.conf fixes the TCP_MISS/503 for the caching as well as enables Office 365 to be accessed through it:
forward_max_tries 25

See [[http://www.squid-cache.org/mail-archive/squid-users/201308/0268.html]] for more information

Associated revisions

Revision 65ff2ae5
Added by Giacomo Sanchietti almost 4 years ago

Merge pull request #4 from SystemEd-Jacob/patch-2

Change forward_max_tries default. Refs #3288

History

#1 Updated by Jacob Oliver almost 4 years ago

  • Target version changed from v6.7 to v6.7-final

#2 Updated by Giacomo Sanchietti almost 4 years ago

  • Status changed from NEW to TRIAGED
  • % Done changed from 0 to 20
  • Security class deleted (low)

The new default for Squid 3.5 is 25, so the patch can safely applied.

Pull request: https://github.com/NethServer/nethserver-squid/pull/4

#3 Updated by Giacomo Sanchietti almost 4 years ago

  • Status changed from TRIAGED to ON_DEV
  • Assignee set to Giacomo Sanchietti
  • % Done changed from 20 to 30

#4 Updated by Giacomo Sanchietti almost 4 years ago

  • Status changed from ON_DEV to MODIFIED
  • % Done changed from 30 to 60

Pull request has been merge.

#5 Updated by Giacomo Sanchietti almost 4 years ago

  • Status changed from MODIFIED to ON_QA
  • Assignee deleted (Giacomo Sanchietti)
  • % Done changed from 60 to 70
Package in nethserver-testing:
  • nethserver-squid-1.3.9-1.2.g65ff2ae.ns6.noarch.rpm
Test case
  • Check the default forward_max_tries value is set to 25
  • Check the bug is not reproducible

#6 Updated by Filippo Carletti almost 4 years ago

  • Affected version changed from v6.7-final to v6.7

#7 Updated by Filippo Carletti almost 4 years ago

  • Target version changed from v6.7-final to v6.7

#8 Updated by Giacomo Sanchietti almost 4 years ago

  • Assignee set to Giacomo Sanchietti

#9 Updated by Giacomo Sanchietti almost 4 years ago

  • Description updated (diff)

#10 Updated by Giacomo Sanchietti almost 4 years ago

  • Status changed from ON_QA to VERIFIED
  • Assignee deleted (Giacomo Sanchietti)
  • % Done changed from 70 to 90

System and Package Version installed
VM KVM - Clean install of Nethserver 6.7 fully updated
Package Installed: nethserver-squid-1.3.9-1.3.gffcb1e7.ns6.noarch

Test Original Problem
Option forward_max_tries is set to 10 (default).

Test Results after update
Test case 1:

[root@localhost ~]# grep forward_max_tries  /etc/squid/squid.conf
forward_max_tries 25

Verified or Reopen
Verified

Note
I don't have access to an Office 356 account, still this fix is a well known workaround.

#11 Updated by Giacomo Sanchietti almost 4 years ago

  • Status changed from VERIFIED to CLOSED
  • % Done changed from 90 to 100
Released in nethserver-updates:
  • nethserver-squid-1.3.10-1.ns6.noarch.rpm

Also available in: Atom PDF