Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs

Dashboard
Notifications
Mark all as read
Q&A

A term that describes frontend redirects

+0
−2

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?

Why does this post require moderator attention?
You might want to add some details to your flag.
Why should this post be closed?

1 comment thread

HTTP redirection status codes (1 comment)

2 answers

+4
−0

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.

Why does this post require moderator attention?
You might want to add some details to your flag.

0 comment threads

+3
−0

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';
Why does this post require moderator attention?
You might want to add some details to your flag.

0 comment threads

Sign up to answer this question »

This community is part of the Codidact network. We have other communities too — take a look!

You can also join us in chat!

Want to advertise this community? Use our templates!