在 IIS 7.0 網站下掛入的 virtual directory 預設是可以執行指令碼的，所以若是使用者上傳了 aspx, 那該 aspx 就可以執行.. 這會是一個很大的安全問題. 要解決這個, 必需在該目錄的處理常式對應中，把指令碼的功能取消. 看來又要做一次大檢查了.

1. 處理常式對應:

 

2. 編輯功能權限，並且把指令碼拿掉。
 

要記得打開 "顥示所有設定"

 

很久沒有用 Word 了, Word 2010 和以前的 Word 2000 實在差很多, 很多東西都找不到, 目錄即是一例, 做了兩次還是記不得, 乾脆做個記錄, 未來大家做 SA 文件時也可以用到.

1. 先在該行按右鍵, 選取樣式 -> 標題 1
 


2. 在常用標籤的地方找到階層式編號, 選擇要用的編號.

 

3. 讓所有的標題 1 都會自動編號, 一樣是用右鍵, 選樣式, 再選更新標題 1 以符合選取範圍.

  


 4. 設定標題 2, 一樣是用右鍵選樣式.

  


5. 最神奇的一步來了, 第二階的編號要用一般的編號, 不能用階層編號, 不然編號會重新開始. 今天就是在這裡搞了很久.

  


6. 一樣要讓編號套用到所有的標題 2 

  


7. 結果, 值得一提, 上面和左邊各有一個快捷工具可以使用.

  

8 最後, 要插入目錄, 它的位置是在 "參考資料" 裡.
 
  

由於網站的user來自全世界各地，而我們網站產生的時間卻是Server的時間
因此需要使用javascript來做一些轉換，讓user看到是他當地的時間

1. Server端產生具有時區的時間字串，用特定的span + class把它包起來, 時間格式 DateTime.ToUniversalTime().ToString("r")
     

<span class="timeString">Fri, 31 Aug 2012 10:57:04 GMT</span>

2. Client端利用jQuery於網頁load的時候將所有時間轉換成當地時間
    這個地方我用了  date.format.js 來轉換成當地時間 (參考  http://blog.stevenlevithan.com/archives/date-time-format  )
   

     $(".timeString").each(function () {
            var content = $(this).text();

            var d = new Date(content);

            if (!isNaN(d)) $(this).text(d.format("yyyy-mm-dd hh:MM tt"));

        }); 
    

這樣user看到的時間就不會錯了

1. 在要匯出的 DB 上, 按右鍵, 選取工作 -->  產生令碼.

 

2. 歡迎頁

 


 3. 選取資料庫
 

4. 設定選項, 記得要選取 "編寫資料的指令碼"
 

5. 選取資料表
 

6. 選擇要匯出的資料表
 

7. 指定 Script 要儲存的位置
 

8. 檢視摘要
 

9. 完工

當使用 WebRequest 來 Get 網址時，出現"已經嘗試太多次自動重新導向"。

通常為對方網站有進行某種判斷。以下為試過的項目。

上次是將 CookieContainer 設定一個 New Net.CookieContainer 即可。

            Dim http As Net.HttpWebRequest = Net.WebRequest.Create(Url)

            http.Method = "GET"

            http.ContentType = "application/x-www-form-urlencoded;"



            http.UserAgent = "Mozilla/5.0 (compatible; MSIE 9.0; Windows NT 6.0; Win64; x64; Trident/5.0)"

            http.CookieContainer = New Net.CookieContainer

            http.Referer = Url

有時 VS2010 會不知原因的方案總管不會自動移到目前編輯的檔案的位置, 有點不方便. 要改回同步, 可以勾選 "在方案總管中追蹤現用項目", 如下圖:

要重開 Visual Studio 才會生效。

在 Application_BeginRequest 可以加入 BlockHacker

    void Application_BeginRequest(object sender, EventArgs e)

    {

        UW.WU.BlockHacker();

    }

可以做一些基本的防駭.

在 Sys_Coonfig 中有兩個參數要設定: WEB_ERROR_ExceptionCountBeforeBlock, WEB_ERROR_ExceptionCountingIntervalInMinutes

另外還有一個參數: WEB_ERROR_DangerousKeywords, 內容請用逗號分隔, 若是發生 Exception 時, Form 或 QueryString 中含有指定的文字, 收到的警告信會標示為高重要性.

從 http://blog.ie-soft.de/post/2007/12/globalasax-events.aspx  抄來的. 留作參考

HttpApplication Events:

Application_AcquireRequestState
Occurs when ASP.NET acquires the current state (for example, session state) that is associated with the current request. 

Application_AuthenticateRequest
Occurs when a security module has established the identity of the user. 

Application_AuthorizeRequest
Occurs when a security module has verified user authorization. 

Application_BeginRequest
Occurs as the first event in the HTTP pipeline chain of execution when ASP.NET responds to a request. 

Application_Disposed
Adds an event handler to listen to the Disposed event on the application. 

Application_EndRequest
Occurs as the last event in the HTTP pipeline chain of execution when ASP.NET responds to a request. 

Application_Error
Occurs when an unhandled exception is thrown. 

Application_PostAcquireRequestState
Occurs when the request state (for example, session state) that is associated with the current request has been obtained. 

Application_PostAuthenticateRequest
Occurs when a security module has established the identity of the user. 

Application_PostAuthorizeRequest
Occurs when the user for the current request has been authorized. 

Application_PostMapRequestHandler
Occurs when ASP.NET has mapped the current request to the appropriate event handler. 

Application_PostReleaseRequestState
Occurs when ASP.NET has completed executing all request event handlers and the request state data has been stored. 

Application_PostRequestHandlerExecute
Occurs when the ASP.NET event handler (for example, a page or an XML Web service) finishes execution. 

Application_PostResolveRequestCache
Occurs when ASP.NET bypasses execution of the current event handler and allows a caching module to serve a request from the cache. 

Application_PostUpdateRequestCache
Occurs when ASP.NET completes updating caching modules and storing responses that are used to serve subsequent requests from the cache. 

Application_PreRequestHandlerExecute
Occurs just before ASP.NET begins executing an event handler (for example, a page or an XML Web service). 

Application_PreSendRequestContent
Occurs just before ASP.NET sends content to the client. 

Application_PreSendRequestHeaders
Occurs just before ASP.NET sends HTTP headers to the client. 

Application_ReleaseRequestState
Occurs after ASP.NET finishes executing all request event handlers. This event causes state modules to save the current state data. 

Application_ResolveRequestCache
Occurs when ASP.NET completes an authorization event to let the caching modules serve requests from the cache, bypassing execution of the event handler (for example, a page or an XML Web service). 

Application_UpdateRequestCache
Occurs when ASP.NET finishes executing an event handler in order to let caching modules store responses that will be used to serve subsequent requests from the cache. 

Application_Init
This method occurs after _start and is used for initializing code. 

Application_Start
As with traditional ASP, used to set up an application environment and only called when the application first starts.

Application_End
Again, like classic ASP, used to clean up variables and memory when an application ends.

Session Events:

Session_Start
As with classic ASP, this event is triggered when any new user accesses the web site.

Session_End
As with classic ASP, this event is triggered when a user's session times out or ends. Note this can be 20 mins (the default session timeout value) after the user actually leaves the site.

Profile Events:

Profile_MigrateAnonymous
Occurs when the anonymous user for a profile logs in.

Passport Events:

PassportAuthentication_OnAuthenticate
Raised during authentication. This is a Global.asax event that must be named PassportAuthentication_OnAuthenticate.
 

Possibly more events defined in other HttpModules like:

System.Web.Caching.OutputCacheModule
System.Web.SessionState.SessionStateModule
System.Web.Security.WindowsAuthentication
System.Web.Security.FormsAuthenticationModule
System.Web.Security.PassportAuthenticationModule
System.Web.Security.UrlAuthorizationModule
System.Web.Security.FileAuthorizationModule
System.Web.Profile.ProfileModule