1

Nginx is used to handle uploading of files in a server (he have registered an action of writting a file, when sent to specific endpoint). There is a master process, responsible for various things, including access states and cookie-like values. From other processes, we use gRPC to communicate with the master process. Right now there is no connection between nginx and this process (so files can be upload whenever we want). Our goal is to make nginx communicate with master process, to find out if the file upload is permitted and also if the request carries this cookie-like value.

Is something like this possible? Can this be done by a new module, that parses the request's body and then communicates with master process via gRPC, to get what it needs? Also, in this case, we need also to take into consideration any timeouts of nginx?

1
  • Just about any way of doing services is possible, but you need to design it first. Please edit your question to fully trace through this workflow. Which of these are separate services: frontend (http?), storage, authorization? Are uploads passed through an application, or is it just nginx allowing POST of files? Draw a service diagram like in Envoy docs: envoyproxy.io/docs/envoy/v1.34.2/intro/life_of_a_request You don't have to use envoy, but its many example use cases make for useful comparisons: could you do the auth thing with envoy external auth filter? Commented Jul 10 at 16:12

0

You must log in to answer this question.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.