124
edits
(→Open Issues & Questions: note about redirectLoop) |
|||
Line 14: | Line 14: | ||
** ok for now will assume "Firefox" will resolve to some environment variable that's accessable from these messaages --[[User:Beltzner|Beltzner]] 14:26, 27 Jul 2005 (PDT) | ** ok for now will assume "Firefox" will resolve to some environment variable that's accessable from these messaages --[[User:Beltzner|Beltzner]] 14:26, 27 Jul 2005 (PDT) | ||
* not sure about [[Firefox:1.5_Network_Error_Messages#redirectLoop|redirectLoop's]] recommendation to turn on cookies; security/privacy issues? | * not sure about [[Firefox:1.5_Network_Error_Messages#redirectLoop|redirectLoop's]] recommendation to turn on cookies; security/privacy issues? | ||
** That does seem to be the correct solution the redirectLoop problem in my experience, security/privacy issues aside. ([http://weather.com weather.com] is/was a particularly bad offender, as blocking cookies from one of its subdomains would cause the infinite redirect loop.) --[[User:Sardisson|Sardisson]] 20:35, 28 Jul 2005 (PDT) | |||
* not sure about [[Firefox:1.5_Network_Error_Messages#deniedPortAccess|deniedPortAccess's]] recommendation about plugins/3rd party apps; could that happen? | * not sure about [[Firefox:1.5_Network_Error_Messages#deniedPortAccess|deniedPortAccess's]] recommendation about plugins/3rd party apps; could that happen? | ||
** I don't think so; plugins should affect protocols, not port security when browsing HTTP. Could be wrong. --[[User:Wrprice|Wrprice]] 12:27, 28 Jul 2005 (PDT) | ** I don't think so; plugins should affect protocols, not port security when browsing HTTP. Could be wrong. --[[User:Wrprice|Wrprice]] 12:27, 28 Jul 2005 (PDT) |
edits