Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Support `@LocalArmeriaPort`, `@LocalArmeriaPorts`
See original GitHub issueI’m working on a PR to allow Armeria internal services and spring actuators to only be allowed on certain ports. But I faced one problem.
When I specify a random port, I can’t tell it clearly. So in Armeria, it would be nice to provide annotations like @LocalArmeriaPort and @LocalArmeriaPorts like @LocalServerPort as Spring Boot provides.
Also, this task will bind to that port when management.server.port is set, and it would be nice to use @LocalManagementPort.
This is likely to be a cornerstone for future features that will be added.
See https://docs.spring.io/spring-boot/docs/current/reference/htmlsingle/#howto-discover-the-http-port-at-runtime
See @LocalRSocketServerPort
Issue Analytics
- State:
- Created 4 years ago
- Comments:8 (5 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Rethinking, it seems that
management.server.portshould be included after the PR or it should be included.This is because allowing a port allows all other routes to access.
Hmm … If so, what do you think of changing the port from Spring integration module to a random port if the port is set to 0?
This solution is not perfect in timing, but it adds nothing to
ServerPort.