REST calls on second interface

[marie-dk]

On Wed, Sep 8, 2010 at 11:37 PM, marie_dk [email protected] wrote:
On 9 Sep., 01:53, Michael Carter [email protected] wrote:

This feature doesn't exist, but it wouldn't be terribly difficult to add. To
be clear: You want to only expose the web/rest api over a specific (private)
interface, and the public protocol over another (outward facing) interface?

Yes, exactly that would be great!
You could just add a second interface option which specifies what
interface the rest api should listen to.

Cool, can you make an issue for this on the github tracker? I will make sure it gets into our 0.4.0 release.

-Michael Carter

[slmnhq]

I've submitted a pull request that implements this feature.

[marie-dk]

http://groups.google.dk/group/hookbox/browse_thread/thread/84a6aa8c1181d328
Michael wrote in this thread, that this addition should implement --web-api-port and --web-api-interface options... but --web-api-interface is missing.

[slmnhq]

1. Can you please post the exact command that you are using?
2. Can you please try the "-w" short form instead?

[slmnhq]

I'm sorry I misunderstood the subtle difference between --web-api-port and --web-api-interface.

The former always listens on localhost. I can see the use case where you don't want it to listen on localhost but on a private LAN interface.

It should be a pretty easy enhancement.

[marie-dk]

I am replicating data between servers with rest calls, and I need these calls to stay private. That is why I wanted to change the interface. The port option on it's own is pretty useless to me :-(
Is there any chance that the --web-api-interface is added in the near future?