Re: FCC

On 02/07/2010 19:31, Jeff Liebermann wrote:
On Fri, 02 Jul 2010 09:31:31 +0100, Bob<bob@xxxxxxxxxxxxxxx> wrote:

For the last couple of years I have had the sendreferer header in
about:config set to "0" and it seems that the FCC website doesn't like
this. Modifying the sendreferer header to "1" allows me to access the
data. Strange that I didn't have problems prior to FF3.6.4-3.6.6.

Nice troubleshooting and sorry about the wrong cookies guess.

The default is "2".
<http://kb.mozillazine.org/Network.http.sendRefererHeader>
Those concerned with privacy can set this to 0, realizing
that this may adversely affect some sites. Those wanting
to ensure compatibility should leave it at the default.
I think the FCC might be using logging software that records the
refering web page. Why not having this information should cause and
authorization error is rather mysterious.


I have just noticed that the "Link" details are different from what they used to be as well.
from alt.internet.wireless 2009
<https://fjallfoss.fcc.gov/prod/oet/forms/blobs/retrieve.cgi?attachment_id=467852&native_or_pdf=pdf>
has become
<https://fjallfoss.fcc.gov/eas/GetApplicationAttachment.html?id=467852>
only accessible via the FCC website.

This will make it difficult to provide a readily accessible link via usenet.
.

Relevant Pages

  • Re: FCC
    ... about:config set to "0" and it seems that the FCC website doesn't like ... Modifying the sendreferer header to "1" allows me to access the ... Strange that I didn't have problems prior to FF3.6.4-3.6.6. ...
    (alt.internet.wireless)
  • Re: FCC
    ... only accessible via the FCC website. ... This will make it difficult to provide a readily accessible link via usenet. ... The first link works without going through the approval ... removing the cookie doesn't seem to do anything. ...
    (alt.internet.wireless)