Menu

#522 trouble with non-standard http port(s)

3.0.x
closed
5
2005-04-29
2005-04-29
csights
No

privoxy 3.0.3, win2000 & linux, firefox 1.0.3

Hi, thank you for the nice filtering proxy.

I have trouble browsing web interfaces to cvs when they
are on non-standard ports. E.g.

https://cvs.cis.upenn.edu:3690/svnroot/unison-contributed-binaries/windows/

With privoxy enabled or disabled Firefox gives me a
completely blank page and IE gives a "HTTP Error 403 -
Forbidden" page.
If I bypass privoxy by changing the connection
settings in either browser to have a direct connection
to the internet the page loads correctly.
It appears as though privoxy doesn't handle the
non-standard port correctly?

Thanks!

Discussion

  • Andreas Oesterhelt

    • labels: --> configuration
    • milestone: --> 3.0.x
    • assigned_to: nobody --> oes
    • status: open --> pending
     
  • Andreas Oesterhelt

    Logged In: YES
    user_id=78811

    No, it's just that all https ports besides 443 are
    forbidden by default, to prevent TCP relaying
    through Privoxy for spam and security considerations.

    To allow the ports you need, you can use the
    limit-connect action. It can be configured through
    http://p.p/ and is documented here:

    http://www.privoxy.org/user-manual/actions-file.html#LIMIT-CONNECT

     
  • Nobody/Anonymous

    Logged In: NO

    Thank you very much for the info! It might be helpful for
    privoxy to display an informative error message instead of a
    blank page?

    C.

     
  • Andreas Oesterhelt

    Logged In: YES
    user_id=78811

    Won't work, since the browser wants to establish
    an encrypted connection afterwards, and won't read
    lest display any document we could send.

    We go as far as we can and send a non-standard
    HTTP-Header: "X-Hint: If you read this message
    interactively, then you know why this happens ,-)"

    IE also seems to be ignoring our HTTP message text -
    what we send is : "403 Connection not allowable"
    which should also hint at the problem being a policy
    issue.

    Cheers,
    -A

     
  • Andreas Oesterhelt

    • status: pending --> closed
     

Log in to post a comment.