Fix to leave alone JSON (or other non-HTML) requests #31
+1
−1
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
+1 |
|
+1, I also am experiencing problems with this |
|
Turns out this repo isn't the version maintained in the gem repo. I've submitted a reworked pull request in the more modern version; benlangfeld#29 |
|
This project is abandoned. Please see the active fork at http://github.com/benlangfeld/mobile-fu. Please test with the released gem and master branch of the new home for the project, and file an issue on the other repo if you still have problems. See #40. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There are applications that handle mobile web clients just as well as API or file (think CSV) requests from mobile devices. That's usually not a problem until the project name contains the "mobi" character sequence, which gets propagated to the User-Agent header, making mobile-fu turn all the non-HTML requests to mobile HTML ones, most possibly leading to a "view not found" error.
Considering that a lot of mobile projects will indeed have the word "mobile" in their name somehow, this fix can be pretty important.