> Source: [sk41280](https://support.checkpoint.com/results/sk/sk41280)

# sk41280 - How to configure FireWall-1 to run the HTTP Security Server on a port other than port 80

| Property | Value |
|----------|-------|
| Solution ID | sk41280 |
| Date Created | 2009-04-19 |
| Last Modified | 2010-04-01 |
| Technical Level | General |
| Products | Security Gateway |
| Versions | R82.10, R82, R81.20 |

## Solution

The following resolution describes how to allow FireWall-1 to allow HTTP traffic on a port other than port 80, while still being able to provide both authentication and content security.

Define each port you wish to allow out and add it to the security policy. Note that if you wish to do authentication or content security for HTTP on these ports, set the protocol type for these services to URI.

If you do not wish to define each port explicitly (or you are not using direct HTTP access for some other reason), you will need to have your web clients use the FireWall as a proxy for HTTP. You will then need to allow HTTP access with a resource defined as follows:

> <br />
>
> Host: \*:\*  
>
> Path: \*  
>
> Query: \*
>
<br />

Note that *any* port will be allowed for http traffic. If you want to limit it to specific ports, you can do it this way:  

<br />

> Host: \*:{80,81,8000,8080}  
>
> Path: \*  
>
> Query: \*

The ports allowed by the above are 80, 81, 8000, and 8080.

If you are not using the HTTP Security Server in proxy mode, you will also need to make sure that $FWDIR/conf/fwauthd.conf has the appropriate lines so that the security servers will monitor 81, 8000, and 8080 as well. The lines should look similar to:

> 21 fwssd in.aftpd wait 0  
>
> 80 fwssd in.ahttpd wait -2  
>
> 81 fwssd in.ahttpd wait 0  
>
> 8000 fwssd in.ahttpd wait 0  
>
> 8080 fwssd in.ahttpd wait 0  
>
> 513 fwssd in.arlogind wait 0  
>
> 25 fwssd in.asmtpd wait 0  
>
> 23 fwssd in.atelnetd wait 0  
>
> 259 fwssd in.aclientd wait 259  
>
> 10081 fwssd in.lhttpd wait 0  
>
> 900 fwssd in.ahclientd wait 900  
>
> 0 fwssd in.pingd respawn 0  
>
> 0 fwssd in.asessiond respawn 0  
>
> 0 fwssd in.aufpd respawn 0  
>
> 0 vpn vpnd respawn 0  
>
> 0 fwssd mdq respawn 0  
>
> 0 xrm xrmd respawn 0 -pr  
>
> 0 stormd stormd respawn 0  
>
> 0 sds sdsd respawn 0  
>
> 0 dtps dtpsd respawn 0  
>
> 0 dtls dtlsd respawn 0  
>
> <br />
>
<br />

<br />

---

# Agent Instructions

This content is from the Check Point Support Center (https://support.checkpoint.com), the official knowledge base for Check Point cybersecurity products.

## Navigating This Knowledge Base

- **Complete index**: [llms.txt](https://support.checkpoint.com/llms.txt)
- **All SK articles**: [SecureKnowledge Sitemap](https://support.checkpoint.com/sitemaps/secureknowledge-sitemap-index.xml)
- **SK article URL pattern**: `https://support.checkpoint.com/results/sk/{skId}`
- **Markdown responses**: AI bot User-Agents automatically receive `text/markdown` content