General mechanism for redirecting to "mobile" or "Basic HTML" sites where necessary

Bug #457400 reported by root
16
This bug affects 1 person
Affects Status Importance Assigned to Milestone
psiphon
Fix Committed
Unknown
Unassigned

Bug Description

Something like what we currently (I think) do for gmail would work for Facebook, as well. We should make this easy to setup as a stopgap measure to support high-priority sites for which we are still working toward proper javascript-compatibility.

Tags: category1
Adam P (adam+)
Changed in psiphon:
status: New → Confirmed
Chris (poser)
tags: added: poser
Chris (poser)
tags: removed: poser
Rod (rod-psiphon)
visibility: private → public
Rod (rod-psiphon)
tags: added: category1
Revision history for this message
Adam Kruger (adam-kruger) wrote :
Changed in psiphon:
milestone: none → 2.5
Changed in psiphon:
status: Confirmed → Fix Committed
Revision history for this message
Chris (poser) wrote :

On the 2.5 development server, http://mobile.twitter.com works but http://twitter.com and https://twitter.com do not allow the sending of tweets.

Revision history for this message
Adam Kruger (adam-kruger) wrote : Re: [Bug 457400] Re: General mechanism for redirecting to "mobile" or "Basic HTML" sites where necessary

Thanks. We'll look at making a custom user agent for twitter.

On Thu, Aug 5, 2010 at 8:14 PM, Chris <email address hidden> wrote:

> On the 2.5 development server, http://mobile.twitter.com works but
> http://twitter.com and https://twitter.com do not allow the sending of
> tweets.
>
> --
> General mechanism for redirecting to "mobile" or "Basic HTML" sites where
> necessary
> https://bugs.launchpad.net/bugs/457400
> You received this bug notification because you are a member of Psiphon
> Inc., which is a direct subscriber.
>
> Status in Psiphon Censorship Circumvention Software: Fix Committed
>
> Bug description:
> Something like what we currently (I think) do for gmail would work for
> Facebook, as well. We should make this easy to setup as a stopgap measure to
> support high-priority sites for which we are still working toward proper
> javascript-compatibility.
>
>
>

Revision history for this message
MichaelMcCarthy (michaelmccarthy1) wrote :

User-Agent Detection: Identify the user's device and browser via the User-Agent header in the HTTP request.

Determine Redirection Need: Decide if redirection is needed, e.g., for mobile or older browsers.

Set Up Redirection Rules:

Server-Side: Use server-side scripting to send an HTTP "Location" header for redirection.

Client-Side (JavaScript): Use JavaScript to update window.location.href.

Offer Full Site Option: Always provide an option for users to switch back to the full (https://mobilecheck.pk/)site.

Testing: Test across devices and browsers to ensure smooth redirection.

Consider Responsive Design: Alternatively, consider responsive design to adapt your site based on user device and screen size for a seamless experience.

i do it in my site

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.