RESTful | A WPF test client for RESTful APIs

Azure Cosmos db is only supporting Unicode or ASCII in x-ms-documentdb-partitionkey while github.com/vippsas/go-cosmosdb package is using json.Marshal which internally transforms Unicode to Chinese characters automatically.

The only way to solve it is using English as partition key when creating documents.

• Why it works on Postman and not on the client code?

The difference is the format of the request. In Postman, you're sending the data as JSON object. While in the client code, you're sending data inside a form-data. They are different. That's why the req.body is empty. Different request formats require the server to parse in different ways.

I see in your code the line //formData.append("thumbnail", newProject.thumbnail); is commented, you prepare to send the project's thumbnail in the request. In this case, you cannot send the request in JSON format. You need to modify the server to make it understand the form data.

For this, I recommend this popular package

Multer is a node.js middleware for handling multipart/form-data, which is primarily used for uploading files.

I have managed to figure out the problem. The issue was related to tomcat configuration in /conf/server.xml. Multiple Hosts will trigger the context loader to be triggered for each. I was keeping the default appBase to webapps for all host thus triggering the ContextLoader of each my war for each host. Another reason the ContextLoader will triggered multiple times as well is defining the option inside unless you need to load something external to your war. I recommend reading specs: https://tomcat.apache.org/tomcat-4.1-doc/config/host.html

Does everything on the World Wide Web use REST?

Sort of.

REST is an architectural style, the "coordinated set of architectural constraints" used in the development of the HTTP 1.1 standard in the 1990s. Notice that Roy Fielding, who describes RESTin the dissertation he published in 2000, is also the first author listed in RFC 2616 (and more recently, RFC 7230).

In chapter six of his dissertation, Fielding observes:

Like most real-world systems, not all components of the deployed Web architecture obey every constraint present in its architectural design.

The tracking of client application state is a common example; the web, as it is today, doesn't offer us a common, general purpose mechanism for tracking state in our clients. So instead, web designers resort to tracking that state on the server, either by using resources specific to a user (see REST mismatches in URI) or by using cookies as a hidden mechanism for tracking history on the server (see REST mismatches in HTTP).

In other words, the web we use every day isn't a perfect expression of the REST architectural style.

Further more, you have ideas like SOAP or GraphQL, where important semantic information about a message is not expressed in a standardized form, which means that our general purpose components cannot assess the semantics of the messages and take intelligent actions.

are all, essentially, web services, RESTful

No - not unless you limit yourself to a definition of "web services" that excludes implementations that violate REST.

Finding web implementations that are architecturally aligned with remote procedure calls, rather than REST, is common. See Fielding 2008. Special note: read the comments, which contain a lot of useful Q and A.

Try:

Remove the below method within the repository interface. The JPA has only find…By, read…By, get…By, query…By, search…By, stream…By.. and so on.

I figured out the issue. I was running both front end and backend in the same project which resulted in API calls from the very same project to ip:8080 was void. I hosted the backend on ip:9090 and the frontend on ip:8080 in order for it to work.

Create a Asp.Net Web Application with Empty template and check Web Api:

After creating the project right click on Controller Folder and select Web Api 2 Controller-Empty Now you have a Restful Api Controller that can be called from any where.(for example from an agular http get request service)

Without having an environment setup or really knowing exactly what you want out of the data. This is a good start.

Generally speaking, the Django ORM is not great for these types of queries, and trying to use select_related or prefetches results in really complex and inefficient queries.

I've found the best way to achieve these types of queries in Django is to break each piece of your puzzle down into a query that returns a "list" of ids that you can then use in a subquery.

Then you keep working down until you have your final output