redirect_uri needs to state type of redirect

[orubel]

So as we all know from the HTTP standard, there are two types of redirects:

• internal redirect (see forward/java, loopback/nodejs, stepfunctions/Lambdas)
• external redirect

Internal redirection is mainly done by multithreaded applications as they have a front controller embedded in the api application rather than abstracted to the app server like in single threaded api apps.

Roy Fieldings dissertation talks about the front controller repeatedly as in how the state of the request/response is maintained :
"There must be some controller object that is responsible for
maintaining the system state in order to complete the application requirements."

And that is the front controller which handles the 'state' because (as the 'front controller' wiki page states):
It is "a controller that handles all requests for a website,"[1] which is a useful structure for web application developers to achieve flexibility and reuse without code redundancy.

However the problerm lies it seems in the fact you all are only implementing an EXTERNAL REDIRECT which seems to target only single threaded applications like Node.js which are only a partial implementation of the HTTP standard for redirection.

Is this the case with this standard or are you planning to support the HTTP standard fully by implementing internal redirection?

This would be fully compliant with Roy Fieldings dissertation on API's.

I hope I provided enough information so people who are not informed in this will not get confused easily and state these concepts are made-up.

I also am reposting because the point got derailed by someone saying this was all made-up when the nomenclature is used widely and throughout the industry.

Fingers crossed on being adults this time.

[darrelmiller]

I am currently sitting in a room with most of the authors of the HTTP specifications (including Roy) over the last few decades and I just asked the question to the room as to whether there there is a distinction between internal redirect and external redirect in the HTTP specification. The consensus of the room is that there is not.

Closing this conversation, once again, as not constructive.

[orubel]

Roy Fielding responded:
"I don’t recall hearing that question (nor it’s context), but the term “internal redirect” was created for NCSA httpd (and continued by Apache) to refer to requests internal to the server implementation (like a file include), in contrast to "external redirect" being an HTTP 3xx response message. Hence, there are no internal redirects in HTTP because they aren’t part of HTTP: they are content handlers within some server code. Note that those content handlers might include sub-requests that use HTTP, but those sub-requests are just normal GET requests to obtain content which is then repackaged with an HTTP success or error response.

My example is the custom error pages in Apache when configured as URLs."

So you obviously did NOT talk to him AND they do exist in API's... just not addressed as part of HTTP standard.

So if you are creating an API standard (not an extended HTTP standard), you have to address the API standard that we are working with in existing tools.

Shall I resubmit the issue now that Roy Fielding says this exists??? I mean little ole me being the researcher that I am, you can call me a liar all day but are you seriously going to call Roy Fielding a liar too???

[orubel]

so I resubmitted and @darrelmiller closed this as 'COMPLETE'.

He was the one who stated: "in a room with most of the authors of the HTTP specifications (including Roy) over the last few decades and I just asked the question to the room as to whether there there is a distinction between internal redirect and external redirect in the HTTP specification. The consensus of the room is that there is not."

And Roy Fielding wrote me back saying Darrel Miller never asked the question and 'internal redirtection' IS A THING for API's!

Sooooo.... not seeing how this is complete or addressed in any way.