Reverse Proxy dest path

[Oryx]

Hi,

I'm running R81.20, JHF take53 and I'm trying to use the ReverseProxy feature.

Everything seems to be working fine, except the <path dest="destpath"/> attribute. When I try to config the dest on the xml file and I run the ReverseProxyCLI apply config, that config is just removed from the file.

I've tried many times wih different rules and it's always the same result. Do you know if this is an expected behaviour or if there are any kind of issue with this particular attribute on this Take?

Thanks in advance,

César Santos

[Lesley]

How does the XML look any mistakes building it? (coding error)

<allowedPaths>             <path source="sourcepath"/>             <path dest="destpath"/>         </allowedPaths>

The allowedPaths define the resources to be reached on the site. The attribute <path source=...> holds the path to which it is mapped. The attribute <path dest=...> defines the path to which it is mapped. You can define multiple paths on the same rule. If <path source=...> is not defined, then the default source is root ( / ). If the <path dest=...> is not defined, then it is the same as the source.

[Oryx]

Hi,

I'm not getting any error when I run the ReverseProxyCli apply config. So, this is a snippet of my ReverseProxyConfig.xml file with the attributte dest properly defined.

Then I apply the config. I'm not getting any kind of errors on the output.

Then, when I cat the file, I'me getting this.

So the dest attribute just got eliminated somehow. I did not find anything on the doc about this behaviour.

Kind regards,

César Santos

 

 

 

[the_rock]

Same here, just tested on R81.20 jumbo 51 lab fws, works fine.

Andy

[Oryx]

So, issue with take53, right?

César

[ajsingh]

Hi,

I am running same issue on R81.10 T150, Any updates on this ?

[Oryx]

Hi,

Never had an official reply from Check Point about this.

To be honest, I did not invested too much energy on this. I've ended up starting a VM with Nginx to make the Reverse Proxy on my end customer. Since the Check Point Security Gateway was a new product for my end customer, I've come to the conclusion that it wasn't the best approach for him to manage the reverse proxy feature on the CLI. He was not technically mature enough for that. 

So, I don't know if this issue was on R81.10 T150.

Kind Regards,

César Santos