Re: HTTP on non standard ports





"Martijn" wrote:

> > It may be useful on some cases, but not in mine.
> > Any ideas on the way I can let people surf only on allowed ports with web
> > filter enabled?
>
> Create new protocol for 8080. And allow only that protocol plus HTTP for the
> Authenticated Users

This is the current setup!
The problem is that allowing the HTTP protocol with WEB filter enabled, it
also matches all other http connection on any port.
In the log I see that the rule that metched was Allow HTTP (that is the rule
like the one you wrote), indicating that destination port was (for example)
12329.
If I unbind the web filter, only port 80 is allowed.

.



Relevant Pages

  • Re: [fw-wiz] tunnel vs open a hole
    ... It does depend on what protocols you are passing through the port or the ... If the protocol is pure HTTP, ... If the protocol is new whizbang multi-media binary with no RFC or complete ... or tunnel over currently open port 80? ...
    (Firewall-Wizards)
  • Re: HTTPhandlers
    ... debates weather or not HTTP is a suitable protocol is not what I am looking ... I need to know how I can have a TcpListener listen on port 80 eventhough IIS ... > which you make the request to do the connection with the user and maintain ... >> HTTP is a stateless protocol. ...
    (microsoft.public.dotnet.framework)
  • Re: disable HTTP Filter for some Users
    ... Internet with NAT (Dest. ... Port 80 - http), ... without the http-filter checked) and a new protocol rule with this protocol. ...
    (microsoft.public.isa)
  • Re: I can receive email but cannot send it.
    ... Webmail is irrelevant - it uses a different port, a different protocol ... (HTTP), and probably accesses a different server altogether. ...
    (microsoft.public.outlook.general)
  • abort at the end of data transfer
    ... data chunk is i.e 6. ... int init_client(int port, char *ip) { ... Protocol Info ... Stream Control Transmission Protocol, Src Port: 1031, Dst Port: ...
    (comp.lang.c)

Quantcast