restful-url

I have exposed some ReSTFul web services on a corporate network [ Company's Internal Network]. I am trying to test those using curl on windows . The address of the GET request is something like this --> (http s on non standard port ) https://myCompanysNet: 13432 /something/something/1.0.0/ curl -H "Accept:application/xml" --user username:password "https://myCompanysNet:13432/something/something/1.0.0/" And I have added option insecure in curlrc conf. file But instead of getting the required XMLs in the response , the output is some html page showing the following error HTTPS Request Blocked

What's the rule of thumb for passing data in a REST URL in the query string vs. the body of a request? Ie: You're creating a service to add hockey players. You could go with: PUT /players { "name": Gretzky } or PUT /players?name=Gretzky If you're passing a lot of data, you would need to go with option #1 as there is a limit on the URL length. But other than this, why not just use the query string to pass data? Update : Removed comment that you could test option #2 in a browser. Realized (duh) that you can only do GET-s in your browser. Based on HTTP's definition of PUT, your first request is

We have a web application which is hosted with the URL http://example.com . Now we want to extend a part of this application as a restful service, and we are debating on the best URL pattern. I searched, but could not find any concrete guidance. Should we have the URL pattern http://api.example.com or http://exaple.com/api/v1 ? Is there any standard guidance for this? Jobert Enamno It depends on your needs. If you use http://api.example.com it makes your API a subdomain. Basically, this URL pattern is good if your REST service is to be consumed by multiple clients, but if only one client is

To my knowledge both serves the same purpose. Except the fact that @PathVariable is from Spring MVC and @PathParam is from JAX-RS. Any insights on this? @PathVariable and @PathParam both are used for accessing parameters from URI Template Differences: As you mention @PathVariable is from spring and @PathParam is from JAX-RS . @PathParam can use with REST only, where @PathVariable used in Spring so it works in MVC and REST. PathParam: To assign URI parameter values to method arguments. In Spring, it is @RequestParam . Eg., http://localhost:8080/books?isbn=1234 @GetMapping("/books/") public Book

I was designing a web app and then stopped to think about how my api should be designed as a RESTful web service. For now, most of my URI's are generic and might apply to various web apps: GET /logout // destroys session and redirects to / GET /login // gets the webpage that has the login form POST /login // authenticates credentials against database and either redirects home with a new session or redirects back to /login GET /register // gets the webpage that has the registration form POST /register // records the entered information into database as a new /user/xxx GET /user/xxx // gets and

I've a Spring application that expose restful endpoints through @RequestMapping annotation in Controller classes. I wish that were logged into the console, at server startup, all the endpoints of all the application's controller. I use a tomcat server and log4j for logging. Thanks. For those who use spring-boot: In the latest spring-boot release (since v2.1), they changed the mapping default log level (as specified in the Release Notes here ). Add one of the following properties to application.properties file: logging.level.web=TRACE logging.level.org.springframework.web=TRACE Sample Console