HTTPS Methods and Status Codes

Here’s a curated list of HTTPS methods and status codes for quick reference by web devs:

METHODS:

• ‘ACL’,
• ‘BIND’,
• ‘CHECKOUT’,
• ‘CONNECT’,
• ‘COPY’,
• ‘DELETE’,
• ‘GET’,
• ‘HEAD’,
• ‘LINK’,
• ‘LOCK’,
• ‘M-SEARCH’,
• ‘MERGE’,
• ‘MKACTIVITY’,
• ‘MKCALENDAR’,
• ‘MKCOL’,
• ‘MOVE’,
• ‘NOTIFY’,
• ‘OPTIONS’,
• ‘PATCH’,
• ‘POST’,
• ‘PRI’,
• ‘PROPFIND’,
• ‘PROPPATCH’,
• ‘PURGE’,
• ‘PUT’,
• ‘REBIND’,
• ‘REPORT’,
• ‘SEARCH’,
• ‘SOURCE’,
• ‘SUBSCRIBE’,
• ‘TRACE’,
• ‘UNBIND’,
• ‘UNLINK’,
• ‘UNLOCK’,
• ‘UNSUBSCRIBE’

STATUS_CODES:

• ‘100’: ‘Continue’,
• ‘101’: ‘Switching Protocols’,
• ‘102’: ‘Processing’,
• ‘103’: ‘Early Hints’,
• ‘200’: ‘OK’,
• ‘201’: ‘Created’,
• ‘202’: ‘Accepted’,
• ‘203’: ‘Non-Authoritative Information’,
• ‘204’: ‘No Content’,
• ‘205’: ‘Reset Content’,
• ‘206’: ‘Partial Content’,
• ‘207’: ‘Multi-Status’,
• ‘208’: ‘Already Reported’,
• ‘226’: ‘IM Used’,
• ‘300’: ‘Multiple Choices’,
• ‘301’: ‘Moved Permanently’,
• ‘302’: ‘Found’,
• ‘303’: ‘See Other’,
• ‘304’: ‘Not Modified’,
• ‘305’: ‘Use Proxy’,
• ‘307’: ‘Temporary Redirect’,
• ‘308’: ‘Permanent Redirect’,
• ‘400’: ‘Bad Request’,
• ‘401’: ‘Unauthorized’,
• ‘402’: ‘Payment Required’,
• ‘403’: ‘Forbidden’,
• ‘404’: ‘Not Found’,
• ‘405’: ‘Method Not Allowed’,
• ‘406’: ‘Not Acceptable’,
• ‘407’: ‘Proxy Authentication Required’,
• ‘408’: ‘Request Timeout’,
• ‘409’: ‘Conflict’,
• ‘410’: ‘Gone’,
• ‘411’: ‘Length Required’,
• ‘412’: ‘Precondition Failed’,
• ‘413’: ‘Payload Too Large’,
• ‘414’: ‘URI Too Long’,
• ‘415’: ‘Unsupported Media Type’,
• ‘416’: ‘Range Not Satisfiable’,
• ‘417’: ‘Expectation Failed’,
• ‘418’: “I’m a Teapot”,
• ‘421’: ‘Misdirected Request’,
• ‘422’: ‘Unprocessable Entity’,
• ‘423’: ‘Locked’,
• ‘424’: ‘Failed Dependency’,
• ‘425’: ‘Too Early’,
• ‘426’: ‘Upgrade Required’,
• ‘428’: ‘Precondition Required’,
• ‘429’: ‘Too Many Requests’,
• ‘431’: ‘Request Header Fields Too Large’,
• ‘451’: ‘Unavailable For Legal Reasons’,
• ‘500’: ‘Internal Server Error’,
• ‘501’: ‘Not Implemented’,
• ‘502’: ‘Bad Gateway’,
• ‘503’: ‘Service Unavailable’,
• ‘504’: ‘Gateway Timeout’,
• ‘505’: ‘HTTP Version Not Supported’,
• ‘506’: ‘Variant Also Negotiates’,
• ‘507’: ‘Insufficient Storage’,
• ‘508’: ‘Loop Detected’,
• ‘509’: ‘Bandwidth Limit Exceeded’,
• ‘510’: ‘Not Extended’,
• ‘511’: ‘Network Authentication Required’

Installing Android on the Geeksphone Keon

Here’s a clean, clear and to the point english post on how to install Android on your Geeksphone Keon developer device:-

STEPS:-

1. If you don’t already have adb and fastboot installed on your system:-
   1. Get the packages from here.
   2. Extract the contents of the zip file and navigate to the adbfastbootmac directory [Note: This package works on macs, if you are using Linux or any other operating system, a simple online search should help you figure out how to get adb and fastboot]
2. On your Keon go to ‘Settings’ -> ‘Device Information’ -> ‘More Information’ -> ‘Developer’. From the list of checkboxes, enable the ‘Remote debugging’ checkbox.
3. Connect your device to your computer using the USB cable.
4. Back on your computer’s terminal do the following:-
   1. If you are using the package mentioned above, run ‘./adb devices’
   2. You should see a device named ‘full_keon’ as a part of the output. If you don’t see it listed out there, try reconnecting your device or check whether the Remote Debugging option is enabled.
5. Now let’s get down to the magic:-
   1. Download and store the following zip packages to you device’s SD-Card:-
      1. TWRP recovery
      2. Android ICS ROM for Keon
      3. Google Apps
      4. Additional Ring Tones
   2. Start the Keon in the fastboot mode :
      # ./adb reboot-bootloader
   3. Install the new recovery :
      # ./fastboot flash recovery TWRP-GK.img
   4. Boot the recovery :
      #./fastboot boot TWRP-GK.img
   5. On the device’s screen now tap on ‘Backup’ to create a backup of Firefox OS.
   6. Once done, tap on ‘Wipe’ → ‘Swipe to Factory Reset’.
   7. ‘Install’ (select the ROM) → ‘Add More Zips’ (select the Google Apps and Additional Ringtones zip files) → ‘Swipe to Confirm Flash’.
   8. ‘Wipe Dalvik and Cache’.
   9. Tap on ‘Reboot System’.
6. Voila! You’ve now successfully installed Android on your Geeksphone Keon device.

NOTES:-

1. Make sure that the device has at least 50% battery power before commencing with the process.
2. Since the Keon has only one soft touch button on it, it is mapped to the back functionality. If you want to use all three default Android soft-buttons, the easiest way to do that would be to install the “SoftKey Enabler” app from the Android Play Store.

SWITCHING BACK TO FIREFOX OS

If you now want to switch back to Firefox OS, all you need to do now is as follows:-

1. Turn off your device.
2. Press the power and the volume up buttons of the Keon at the same time to boot into the Team Win Recovery image.
3. Tap ‘Restore’ and select the backup file created earlier during the Android setup, and confirm.
4. Once the process completes, you should be able to use Firefox OS again! 🙂

DISCLAIMER: Please note that the steps I’ve mentioned here are what I followed to try out Android on a couple of my Keons. These steps involve flashing the device, hence involve a very real risk of ending up with a bricked [dead] phone. As such, go about the process at your own risk. I’m in no way liable for any unforeseen results coming out of this process.

References:

1. http://sys.nodo21.org/geeksphone-keon-rom
2. http://forum.geeksphone.com/index.php?topic=5672.msg60983#msg60983