The HAL Browser doesn't get autoconfigured correctly in spring-data-rest

2
votes

I have install HAL Browser in my spring boot app.

In the documentation they say it will be started at http://localhost:8080.

but it got started at http://localhost:8080/api which is my repositories.

So it override the base path of my spring-data-rest api.

Then inside the HAL browser app, I can see all of my repositories.

If I try a GET, it try's to query them under http://localhost:8080/api/api/entities , which return 404.

The original endpoint http://localhost:8080/api/entities also return 404.

Is the plugin broken with latest spring, spring-data, spring-hateoas modules ?

If I change the data rest api path to "/" it work fine.

Also, I would like to know if it's possible to authorize the client using OAuth. I use spring-security-oauth and all the request are rejected .

Edit It appear the plugin doesn't support different path than / Also, it is not possible to support spring-data-oauth, my best chance is to install HAL Browser my self

1
springspring-bootspring-dataspring-data-resthal
It will get started on the URL you provided for your rest endpoints, which by default is root. Used it in a workshop last week without any problems, so I would say the flaw is in your configuration / setup. – M. Deinum
Well, my rest endpoint is at /api, so this is why the HAL browser start under that path. However, this break my api and doesn't tell me why HAproxy use wrong link at the beginning – Dimitri Kopriwa
What has HAProxy to do with this?! – M. Deinum
Sorry I wanted to write HAL browser ! – Dimitri Kopriwa
Add some code/configuration to your question if you want an answer. – M. Deinum

1 Answers

1
votes

You don't need to use complete URL like http://localhost:8080/api/entities You should use only the URI like - /api/api/entities