Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"Interfaces" parameter does not filter requests #51

Open
mrudelle opened this issue Apr 26, 2017 · 5 comments
Open

"Interfaces" parameter does not filter requests #51

mrudelle opened this issue Apr 26, 2017 · 5 comments

Comments

@mrudelle
Copy link
Contributor

When I set the "interfaces" parameter on two reverseSite so that each handle a different interface, all requests to both interfaces land on the same site.

I created the following super simple example:

http: {
	reverseInterfaceHTTP: {
		type: 'reverse',
		port: 8041,
	},
	reverseInterfaceHTTPS: {
		type: 'reverse',
		port: 8042,
	},
},
@mykiimike
Copy link
Contributor

yo, you can use the interfaces json key into the reverse website configuration. Explained here https://github.com/binarysec/gate/wiki/ConfigurationHttpReverse#website-configuration

All the best

@mrudelle
Copy link
Contributor Author

@mykiimike it seems like site.solvedInterfaces and site.interfaces is not used anywhere in the code. I tried what's in this wiki but without success.

@Dagrut
Copy link
Contributor

Dagrut commented Jun 13, 2017

I added the branch "issue51" which should fix this, but it has to be tested before integration. Tell us if it works for you :-)

@Dagrut Dagrut reopened this Jun 13, 2017
@mykiimike
Copy link
Contributor

Q: This match for a website on * interfaces?

@Dagrut
Copy link
Contributor

Dagrut commented Jun 13, 2017

Well.. Now yes :-p

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants