I have been doing some extensive research into this and other REST paging related questions lately and thought it constructive to add some of my findings here. I’m expanding the question a bit to include thoughts on paging as well as the count as they are intimitely related. Headers The paging metadata is included in … Read more
This worked for me: curl -v –cookie “USER_TOKEN=Yes” http://127.0.0.1:5000/ I could see the value in backend using print(request.cookies)
Yes, you are wrong in mapping CRUD to HTTP methods. Despite the popular usage and widespread misconception, including high-rated answers here on Stack Overflow, POST is not the “correct method for creating resource”. The semantics of other methods are determined by the HTTP protocol, but the semantics of POST are determined by the target media … Read more
I’m not completely sure how your data is handled, so this may or may not work, but have you considered paginating with a timestamp field? When you query /foos you get 100 results. Your API should then return something like this (assuming JSON, but if it needs XML the same principles can be followed): { … Read more
When you use multipart file you don’t set the Content-Type, and it will default to multipart/form-data. Which is most likely what you want – but no one will be able to tell without details about your server. Work with someone from your server-side team if needed to resolve this. Or edit your question with a … Read more
The Web Application Description Language (WADL) is basically the equivalent to WSDL for RESTful services but there’s been an ongoing controversy whether something like this is needed at all. Joe Gregorio has written a nice article about that topic which is worth a read.
It’s up to you. All the approaches are perfectly fine from a REST perspective. According to Roy Thomas Fielding’s dissertation*, any information that can be named can be a resource: 5.2.1.1 Resources and Resource Identifiers The key abstraction of information in REST is a resource. Any information that can be named can be a resource: … Read more
What doesn’t make sense: distributed transactions with REST services. REST services by definition are stateless, so they should not be participants in a transactional boundary that spans more than one service. Your user registration use case scenario makes sense, but the design with REST microservices to create User and Wallet data is not good. What … Read more
@Bacon-Bits answer didn’t seem to work for me. My server rejected it with a potentially malformed form-data body 🙁 I found this gist, and trimmed it up a bit for my purposes. Here’s my end result: $FilePath=”c:\temp\temp.txt”; $URL = ‘http://your.url.here’; $fileBytes = [System.IO.File]::ReadAllBytes($FilePath); $fileEnc = [System.Text.Encoding]::GetEncoding(‘UTF-8’).GetString($fileBytes); $boundary = [System.Guid]::NewGuid().ToString(); $LF = “`r`n”; $bodyLines = ( … Read more
REST is not a specific web service but a design concept (architecture) for managing state information. The seminal paper on this was Roy Thomas Fielding’s dissertation (2000), “Architectural Styles and the Design of Network-based Software Architectures” (available online from the University of California, Irvine). First read Ryan Tomayko’s post How I explained REST to my … Read more