ilake

// reference : http://stackoverflow.com/questions/7203304/warning-cant-verify-csrf-token-authenticity-rails
//            : http://stackoverflow.com/questions/8511695/rails-render-json-session-lost 
  
$.ajax({ url: 'YOUR URL HERE',
  type: 'POST',
  beforeSend: function(xhr) {
    xhr.setRequestHeader('X-CSRF-Token', $('meta[name="csrf-token"]').attr('content'))
  },
  data: 'someData=' + someData,
  success: function(response) {

ilake

# base on ruby 1.9
# Reference :
# http://stackoverflow.com/questions/185947/ruby-define-method-vs-def
# define_method is a (private) method of the object Class. You are calling it from an instance. There is no instance method called define_method, so it recurses to your method_missing, this time with :define_method (the name of the missing method), and :screech (the sole argument you passed to define_method).
# http://stackoverflow.com/questions/752717/how-do-i-use-define-method-to-create-class-methods
class Base
  def self.meta_instance_method &block
    define_method "ins", block
  end

ilake

git config --global user.name "ilake"
git config --global user.email "iamilake@gmail.com"

git config --global alias.co checkout
git config --global apply.whitespace nowarn

git commit -v 
git commit -v -a
git branch -a

ilake

/**
 * http://github.com/Valums-File-Uploader/file-uploader
 *
 * Multiple file upload component with progress-bar, drag-and-drop.
 *
 * Have ideas for improving this JS for the general community?
 * Submit your changes at: https://github.com/Valums-File-Uploader/file-uploader
 *
 * VERSION 2.0 beta
 * Original version 1.0 © 2010 Andrew Valums ( andrew(at)valums.com )

ilake

作者: iincho (..) 看板: Soft_Job
標題: [翻譯] 圖形計算機的故事
時間: Tue Mar  4 12:04:50 2008


Copyright (c) 2004 Ron Avitzur.

============================================================
本文譯自 http://www.pacifict.com/Story/
已獲得作者授權翻譯並同意於 PTT 發布

ilake

reference

• http://rack.rubyforge.org/doc/classes/Rack/Response.html
• http://www.ruby-doc.org/stdlib-1.9.3/libdoc/open3/rdoc/Open3.html
• http://api.rubyonrails.org/classes/ActiveSupport/SafeBuffer.html
• http://apidock.com/ruby/Module/module_function
• http://markdalgleish.com/2011/03/self-executing-anonymous-functions/
• http://stackoverflow.com/questions/5764005/what-is-return-function-used-for-in-javascript
• http://stackoverflow.com/questions/3360858/why-use-in-the-name-of-javascript-variables
• http://stackoverflow.com/questions/1051782/jquery-this-vs-this
• http://api.jquery.com/is/

ilake

# config/initializers/devise.rb
# for web
config.omniauth :google_oauth2, ENV['GOOGLE_CLIENT_ID'], ENV['GOOGLE_CLIENT_SECRET'],
  { access_type: "offline",
    prompt: "consent",
    select_account: true,
    provider_ignores_state: true,
    scope: "plus.profile.emails.read,calendar,contacts" }

# for api

ilake

let result = await fetch({
  api: "http://localhost:3000/users/auth/google_oauth2_for_api/callback",
  method: 'get',
  params: {
    code: response.params.code,
    redirect_uri: redirectUrl
  }
})

// The result is from rails side.

ilake

let redirectUrl = Expo.AuthSession.getRedirectUrl();
let response = await Expo.AuthSession.startAsync({
  authUrl:
  `https://accounts.google.com/o/oauth2/v2/auth?` +
  `&client_id=${GOOGLE_WEB_APP_ID}` +
  `&redirect_uri=${encodeURIComponent(redirectUrl)}` +
  `&response_type=code` +
  `&access_type=offline` +
  `&prompt=consent` +
 `&scope=${encodeURIComponent('https://www.googleapis.com/auth/plus.profile.emails.read https://www.googleapis.com/auth/calendar https://www.googleapis.com/auth/contacts')}`,

ilake

http://sumongh.javaeye.com/blog/82498

理解session機制

session機制是一種服務器端的機制，服務器使用一種類似於散列表的結構（也可能就是使用散列表）來保存信息。
當程序需要為某個客戶端的請求創建一個session的時候，服務器首先檢查這個客戶端的請求裡是否已包含了一個session標識 - 稱為 session id，如果已包含一個session id則說明以前已經為此客戶端創建過session，服務器就按照session id把這個 session檢索出來使用（如果檢索不到，可能會新建一個），如果客戶端請求不包含session id，則為此客戶端創建一個session並且生成一個與此session相關聯的session id，session id的值應該是一個既不會重複，又不容易被找到規律以仿造的字符串，這個 session id將被在本次響應中返回給客戶端保存。

保存這個session id的方式可以採用cookie，這樣在交互過程中瀏覽器可以自動的按照規則把這個標識發揮給服務器。一般這個cookie的名字都是類似於SEEESIONID，而。比如weblogic對於web應用程序生成的cookie，JSESSIONID= ByOK3vjFD75aPnrF7C2HmdnV6QZcEbzWoWiBYEnLerjQ99zWpBng!-145788764，它的名字就是 JSESSIONID。

由於cookie可以被人為的禁止，必須有其他機制以便在cookie被禁止時仍然能夠把session id傳遞迴服務器。經常被使用的一種技術叫做URL重寫，就是把session id直接附加在URL路徑的後面，附加方式也有兩種，一種是作為URL路徑的附加信息，表現形式為http://...../xxx;jsessionid= ByOK3vjFD75aPnrF7C2HmdnV6QZcEbzWoWiBYEnLerjQ99zWpBng!-145788764