Welcome to the Power Users community on Codidact!
Power Users is a Q&A site for questions about the usage of computer software and hardware. We are still a small site and would like to grow, so please consider joining our community. We are looking forward to your questions and answers; they are the building blocks of a repository of knowledge we are building together.
A term that describes frontend redirects
We can talk about backend redirects when we redirect a user from example.com/1.html to example.com/2.html (without a link); the server is asked to do it by some backend-language such as PHP or by JavaScript and a 301/302 redirect is logged as done.
But let's assume that we present two different pseudo-webpages in just one given true webpage; say, we ask the server to show document X in a modal and we also ask the server that if a certain condition was met, react that document Y would be shown instead (we "frontendly redirect" the user from one pseudo-webpage to another pseudo-webpage).
Is there a term to describe such "frontend redirects" with the current web standards?
2 answers
As already stated, of course it's possible to do a redirection in the front end by telling the browser to request a different URL. Using Javascript is one possible method (some companies apparently actually do that); using <meta http-equiv="refresh"> is another. With the Javascript approach, you can even have the client pick the target URL based on some heuristic that is impractical to determine on the server.
However, that's not what you appear to discuss in your question.
What you are asking about seems to be whether it's possible to have the server "react" to some (unspecified here) condition by showing either "document X" or "document Y" in a modal in a larger web page. (Keeping in mind that a web page "modal" is really a web page, client construct; it's only modal insofar as something in the web page itself makes the other parts of the web page inaccessible while the modal is being displayed.)
Which, of course, is also possible. But since the server is making the selection, it can't be front-end, because front-end is generally in these contexts taken to mean something done by the client. Which, when considering web pages, will typically but not always be a web browser.
To do what you are asking, the two obvious options are to either include the raw file contents in the larger page using whatever means your web development stack provides for that, or include the URL to one page or another as a document reference (for example for an <iframe> source). In the former case the contents of that file must fit appropriately wherever it gets included; in the latter case, the page referenced must be a complete web page in its own right.
No front-end logic required.
0 comment threads
You can certainly send the user to a different page from the front end with a bit of JavaScript:
location.href = 'https://example.com/new-page';
0 comment threads
1 comment thread