Cara membuat inject internet dengan VB6

Dalam membuat aplikasi injector yang harus patut kita ketahui adalah alamat proxy provider dan portnya dan juga http header yang nantinya untuk proses injeksi ke proxy provider. Aplikasi injcetor sebenarnya adalah sebuah aplikasi server proxy sederhana yang di modifikasi sedemikian rupa untuk memanipulasi data yang akan di kirim ke proxy provider. Setiap provider akan berbeda topologi / alur modifikasi pengiriman data nya tapi bila anda sudah tau dasar dari aplikasi ini anda bisa dengan mudah menyesuaikan dengan provider yang anda gunakan.

Dalam studi kasus ini kami mengambil sample provider XL dan menggunakan pemrogramam Visual Basic, dan sekali lagi kalau anda sudah paham dasarnya anda bisa implementasikan dengan semua bahasa pemrograman , baik delphi,c#/c++,phyton bahkan java. Di sini kami tidak hanya akan memberikan source code nya saja tetapi beserta penjelasanya jadi anda tau apa sebenarnya yang terjadi dalam setiap prosesnya dan bisa menyimpulkan dasar dari sebuah aplikasi injector, karena di sini kami tidak mengajarkan anda untuk membuat aplikasi instan tapi mengajarkan andan utnuk mengetahui bagai mana sistrem kerja proxy dan membuat aplikasinya dengan benar.

Sebelum kita mulai kita harus mengetahui hal sebagi berikut:

Studikasus Provider XL
IP proxy = 202.152.240.50
Port proxy = 8080


Data header injeksi = “DELETE http://news.okezone.com/ HTTP/1.1" & vbCr & "Host:news.okezone.com" & vbCr & vbCr” Mulailah dengan project baru, pilih standar EXE



Maka akan tampil form seperti pada gambar di bawah



Kita membutuhkan component tambahan yakni winsock, untuk menabahkan component kita bias melalui tahapan seperti pada gambar berikut





Maka akan tampak pada sebelah kiri bertambah icon winsock seperti berikut



Mari kita mulai , yang pertama yang kita butuhkan adalah berikut beserta seting Propertiesnya

• -Winsock1 

Name = sockLokal
Index = 0

• Winsock2 

Name = sockProxy
Index = 0

• textbox name = listenPort text = 2222 
• CommandButton 

Caption = ON

• Timer1 

Index=0
Interval = 1000 Enable = false


Maka akan tampil di form sebagai berikut



Kita membutuhkan 2 winsock berikut penjelasanya

• sockLokal bertugas sebagai pengirim dan penerima data dari komputer kita
• sockProxy bertugas sebagai pengirim dan menerima data dari proxy provider

Kenapa winsock dan timer index kita isikan 0 , karena di sini kita kan membuat jalur multy koneksi jadi winsock dan timer harus berupa array dan patut untuk di mengerti sebuah array di mulai dari 0 bukan 1. Memulai Coding

‘CODE___
Option Explicit
Dim dataLokal(255) As String
Dim dataInject As String
Dim i, cek As Integer
‘CODE___


Yang pertama kita lakukan adalah deklarasi vriabel yang di butuhkan

•  “dataLokal(255)” , berfungsi untuk menyimpan data yang di ambil dari “sockLokal”, perhatikan “(255)” ini menandakan bahwa variable “dataLokal” berupa array dan maksimal arraynya sebanyak 255 

• “dataInject”, berfungsi untuk menyimpan sebuah data http header yang nantinya akan di kirim ke proxy provider yang bertujuan untuk melakukan kamulfase data , atau yang sering orang2 bilang “host” header. 

================================================================================

‘CODE___
Private Sub Form_Load()
dataInject = "DELETE http://news.okezone.com/ HTTP/1.1" & vbCr & "Host:news.okezone.com" & vbCr & vbCr End Sub
‘CODE___ 

Proses diatas menerangakan pengisian “dataInject” dengan data http header , pada saat form di load, dan perhatikan
“vbCr” yaitu merupakan sebuah karakter newline atau garis baru ada 3 tipe newline di visual basic 

vbCr = untuk system unix/linux 

vbLf = untuk system mac 

vbCrLf = untuk system windows tergantung kebutuhan dan kondisi kita akan menggunakan yang mana .
================================================================================


‘CODE___
Private Sub sockLokal_ConnectionRequest(Index As Integer, ByVal requestID As Long) i = i + 1
Load sockLokal(i)
Load sockProxy(i) Load Timer1(i) sockLokal(i).Close
sockLokal(i).Accept requestID
End Sub
‘CODE___ 

Fungsi di atas berfungsi sebagai penerimaan request data yang datang melalui “sockLokal” dan sekaligus melakukan proses load winsock dan timer untuk menentukan array keberapa berdasar request yang di terima.
================================================================================

‘CODE___
Private Sub sockLokal_DataArrival(Index As Integer, ByVal bytesTotal As Long) sockLokal(Index).GetData dataLokal(Index)
If InStr(dataLokal(Index), "GET ") > 0 Then
sockLokal(Index).Close
Exit Sub
End If
If sockProxy(Index).State = 0 Then
sockProxy(Index).RemoteHost = "202.152.240.50" sockProxy(Index).RemotePort = 8080 
sockProxy(Index).Connect
End If
If sockProxy(Index).State = 7 Then
sockProxy(Index).SendData dataLokal(Index)
End If
End Sub
‘CODE___ 

Fungsi di atas berjalan ketika proses koneksi sudah terjalin antara komputer kita ke sockLokal, Fungsi if pertama berguna untuk memutus koneksi ketika di deteksi ada request “GET” daari komputer kita ( mengatisipasi agar program injector tidak bias langsung di gunakan di browser /direct/polos),If yang ke dua berfungsi membangun koneksi ke proxy provider jika kondisi /status koneksi belum terhubung, IF yang ketiga jika koneksi sudah terhubung maka data dari “sockLokal” akan di kirimkan ke proxy provider melalui “sockProxy”
================================================================================

‘CODE___
Private Sub sockProxy_Connect(Index As Integer) sockProxy(Index).SendData dataInject cek = 0
Timer1(Index).Enabled = True
End Sub
‘CODE___ 


Fungsi di atas berjalan ketika “sockProxy” prtama kali terkoneksi dengan proxy provider, kemudia melakukan proses pengiriman data “dataInject” ke proxy provider untuk membuka jalur ke proxy provider yang nantinya akan di kirim data yang sebenarnya dari “sockLokal”, perhatikan variable “cek” kita isikan 0 untuk menandakan bahwa data sebenarnya belum di kirim, kemudian me enable/ mengaktifkan timer1.


================================================================================

‘CODE___
Private Sub Timer1_Timer(Index As Integer)
If cek = 0 Then
If sockProxy(Index).State = 7 Then
sockProxy(Index).SendData dataLokal(Index)
End If
End If
Timer1(Index).Enabled = False
End Sub
‘CODE___ 


Fungsi di atas berjalan ketika “Timer1” di aktifkan / enable’kan, dia akan mengecek apakah data sebenarnya sudah di kirim atau belum berdasar isi dari variable “cek”, jika belum / atau nilainya 0 maka akan di lakukan proses pengiriman data yang sebenarnya ke proxy provider, kemudian menonaktifkan “timer1” itu sendiri agar tidak mengirim data secara terus menerus.


================================================================================

‘CODE___
Private Sub sockProxy_DataArrival(Index As Integer, ByVal bytesTotal As Long)
Dim dataProxy As String
sockProxy(Index).GetData dataProxy
If cek = 1 Then
If sockLokal(Index).State = 7 Then
sockLokal(Index).SendData dataProxy
End If
Else
cek = 1
End If
End Sub
‘CODE___ 

Fungsi di atas berjalan ketika koneksi ke proxy provider sudah terjalin melalui “sockProxy”, kemudian membuat variable baru untuk menampung data respon sementara dari proxy provider dengan nama “dataProxy” .

Perhatikan proses di awal tadi kita sudah mengirimkan 2 kali request ke proxy provider yang pertama data inject dan data aslinya, nah otomatis respon juga akan menjadi dua tipe yang pertama respon dari data inject kemudian yang kedua respon dari data sebenarnya / asli, maka kita akan memilih data yang akan kita kirim ke komputer kita adalah respon yang data asli bukan data inject dengan cara mengecek nilai dari variable “cek” , pada proses sebelumnya “cek” masih bernilai 0 , maka kita lihat jika “cek” bernilai 1 maka respon dari proxy provider akan di kirim ke komputer melalui “sockLokal”, kapan nilai “cek” 1 ? Pada fungsi ini merupakan perulangan jadi respon pertama dalah dari respon inject dan kemudian kita mengisi nilai “cek” 1 maka akan terjadi perulangan lagi untuk respon ke dua dan nilai “cek” sudah 1. Semoga anda mengerti :D
================================================================================

‘CODE___
Private Sub sockProxy_Close(Index As Integer) sockProxy(Index).Close sockLokal(Index).Close
End Sub
‘CODE___ 

Fungsi di atas berjalan ketika jalur koneksi ke proxy provider terputus baik itu karena erro/atau di putus dari provider, maka semua jalur akan di putus baik jalur “sockProxy” atau “sockLokal” untuk mengantisipasi koneksi menjadi bengong :D
================================================================================

‘CODE___
If tombol.Caption = "ON" Then tombol.Caption = "OFF"
sockLokal(0).LocalPort = listenPort.Text sockLokal(0).Listen Else
tombol.Caption = "ON" sockLokal(0).Close
End If
‘CODE___ 

Fungsi di atas berjalan ketika tombol “ON” di klik, kami tidak akan menerangkan silahkan lihat sendiri dan pahami fungsi di atas :D



SOURCE CODE LENGKAP: 

Option Explicit
Dim dataLokal(255) As String
Dim dataInject As String
Dim i, cek As Integer Private Sub Form_Load()
dataInject = "DELETE http://news.okezone.com/ HTTP/1.1" & vbCr & "Host:news.okezone.com" & vbCr & vbCr End Sub
Private Sub sockLokal_ConnectionRequest(Index As Integer, ByVal requestID As Long) i = i + 1
Load sockLokal(i)
Load sockProxy(i) Load Timer1(i) sockLokal(i).Close
sockLokal(i).Accept requestID 

End Sub

Private Sub sockLokal_DataArrival(Index As Integer, ByVal bytesTotal As Long) sockLokal(Index).GetData dataLokal(Index) If InStr(dataLokal(Index), "GET ") > 0 Then
sockLokal(Index).Close
Exit Sub
End If
If sockProxy(Index).State = 0 Then
sockProxy(Index).RemoteHost = "202.152.240.50" sockProxy(Index).RemotePort = 8080 
sockProxy(Index).Connect
End If
If sockProxy(Index).State = 7 Then
sockProxy(Index).SendData dataLokal(Index)
End If
End Sub
Private Sub sockProxy_Connect(Index As Integer) sockProxy(Index).SendData dataInject cek = 0
Timer1(Index).Enabled = True
End Sub
Private Sub Timer1_Timer(Index As Integer)
If cek = 0 Then
If sockProxy(Index).State = 7 Then
sockProxy(Index).SendData dataLokal(Index)
End If
End If
Timer1(Index).Enabled = False
End Sub
Private Sub sockProxy_DataArrival(Index As Integer, ByVal bytesTotal As Long)
Dim dataProxy As String
sockProxy(Index).GetData dataProxy
If cek = 1 Then
If sockLokal(Index).State = 7 Then
sockLokal(Index).SendData dataProxy
End If
Else
cek = 1 End
if
End Sub
Private Sub sockProxy_Close(Index As Integer) sockProxy(Index).Close sockLokal(Index).Close End Sub
Private Sub tombol_Click() If tombol.Caption = "ON" Then tombol.Caption = "OFF" sockLokal(0).LocalPort = listenPort.Text
sockLokal(0).Listen Else tombol.Caption = "ON" sockLokal(0).Close
End If
End Sub

Thanks To http://www.fb.com/kopaci.kopaci

Analysis protokol TCP, UDP, dan SSL

Pada artikel kali ini saya akan sedikit mengupas tentang protocol TCP, UDP, dan SSL.

TCP (Transmission Control Protocol) adalah salah satu protokol yang umun digunakan dalam dunia internet, karena TCP mempunyai kelebihan yaitu adanya koreksi kesalahan. Dengan menggunakan protokol TCP, maka proses pengiriman akan terjamin dengan adanya bagian untuk sebuah metode yang disebut flow control.

UDP (User Datagram Protocol) adalah protokol umum lainnya yang digunakan di dunia internet dan merupakan connectionless. UDP tidak pernah digunakan untuk mengirim data penting seperti halaman web, informasi database, dan sebagainya. Tetapi UDP biasanya digunakan untuk streaming audio dan video, karena UDP mempunyai kelebihan yaitu pada kecepatan transfer. UDP lebih cepat dari TCP karena pada protokol UDP tidak ada bentuk kontrol aliran dan koreksi kesalahan.


Download Tulisan Lengkap: TCP-UDP-dan-SSL.pdf

Definisi Status Code

Pada kesempatan kali ini saya posting tentang Definisi Status Code. mohon maaf saat ini saya tidak sempat mentranslate

100 Continue

The client SHOULD continue with its request. This interim response is used to inform the client that the initial part of the request has been received and has not yet been rejected by the server. The client SHOULD continue by sending the remainder of the request or, if the request has already been completed, ignore this response. The server MUST send a final response after the request has been completed.

101 Switching Protocols

The server understands and is willing to comply with the client's request, via the Upgrade message header field (section 14.42), for a change in the application protocol being used on this connection. The server will switch protocols to those defined by the response's Upgrade header field immediately after the empty line which terminates the 101 response.
The protocol SHOULD be switched only when it is advantageous to do so. For example, switching to a newer version of HTTP is advantageous over older versions, and switching to a real-time, synchronous protocol might be advantageous when delivering resources that use such features.

Successful 2xx

This class of status code indicates that the client's request was successfully received, understood, and accepted.

200 OK

The request has succeeded. The information returned with the response is dependent on the method used in the request, for example:
GET an entity corresponding to the requested resource is sent in the response;
HEAD the entity-header fields corresponding to the requested resource are sent in the response without any message-body;
POST an entity describing or containing the result of the action;
TRACE an entity containing the request message as received by the end server.

201 Created

The request has been fulfilled and resulted in a new resource being created. The newly created resource can be referenced by the URI(s) returned in the entity of the response, with the most specific URI for the resource given by a Location header field. The response SHOULD include an entity containing a list of resource characteristics and location(s) from which the user or user agent can choose the one most appropriate. The entity format is specified by the media type given in the Content-Type header field. The origin server MUST create the resource before returning the 201 status code. If the action cannot be carried out immediately, the server SHOULD respond with 202 (Accepted) response instead.
A 201 response MAY contain an ETag response header field indicating the current value of the entity tag for the requested variant just created.

202 Accepted

The request has been accepted for processing, but the processing has not been completed. The request might or might not eventually be acted upon, as it might be disallowed when processing actually takes place. There is no facility for re-sending a status code from an asynchronous operation such as this.
The 202 response is intentionally non-committal. Its purpose is to allow a server to accept a request for some other process (perhaps a batch-oriented process that is only run once per day) without requiring that the user agent's connection to the server persist until the process is completed. The entity returned with this response SHOULD include an indication of the request's current status and either a pointer to a status monitor or some estimate of when the user can expect the request to be fulfilled.

203 Non-Authoritative Information

The returned metainformation in the entity-header is not the definitive set as available from the origin server, but is gathered from a local or a third-party copy. The set presented MAY be a subset or superset of the original version. For example, including local annotation information about the resource might result in a superset of the metainformation known by the origin server. Use of this response code is not required and is only appropriate when the response would otherwise be 200 (OK).

204 No Content

The server has fulfilled the request but does not need to return an entity-body, and might want to return updated metainformation. The response MAY include new or updated metainformation in the form of entity-headers, which if present SHOULD be associated with the requested variant.
If the client is a user agent, it SHOULD NOT change its document view from that which caused the request to be sent. This response is primarily intended to allow input for actions to take place without causing a change to the user agent's active document view, although any new or updated metainformation SHOULD be applied to the document currently in the user agent's active view.
The 204 response MUST NOT include a message-body, and thus is always terminated by the first empty line after the header fields.

205 Reset Content

The server has fulfilled the request and the user agent SHOULD reset the document view which caused the request to be sent. This response is primarily intended to allow input for actions to take place via user input, followed by a clearing of the form in which the input is given so that the user can easily initiate another input action. The response MUST NOT include an entity.

206 Partial Content

The server has fulfilled the partial GET request for the resource. The request MUST have included a Range header field (section 14.35) indicating the desired range, and MAY have included an If-Range header field  to make the request conditional.
The response MUST include the following header fields:

      - Either a Content-Range header field (section 14.16) indicating
        the range included with this response, or a multipart/byteranges
        Content-Type including Content-Range fields for each part. If a
        Content-Length header field is present in the response, its
        value MUST match the actual number of OCTETs transmitted in the
        message-body.

      - Date

      - ETag and/or Content-Location, if the header would have been sent
        in a 200 response to the same request

      - Expires, Cache-Control, and/or Vary, if the field-value might
        differ from that sent in any previous response for the same
        variant

If the 206 response is the result of an If-Range request that used a strong cache validator (see section 13.3.3), the response SHOULD NOT include other entity-headers. If the response is the result of an If-Range request that used a weak validator, the response MUST NOT include other entity-headers; this prevents inconsistencies between cached entity-bodies and updated headers. Otherwise, the response MUST include all of the entity-headers that would have been returned with a 200 (OK) response to the same request.
A cache MUST NOT combine a 206 response with other previously cached content if the ETag or Last-Modified headers do not match exactly.
A cache that does not support the Range and Content-Range headers MUST NOT cache 206 (Partial) responses.

Redirection 3xx

This class of status code indicates that further action needs to be taken by the user agent in order to fulfill the request. The action required MAY be carried out by the user agent without interaction with the user if and only if the method used in the second request is GET or HEAD. A client SHOULD detect infinite redirection loops, since such loops generate network traffic for each redirection.

      Note: previous versions of this specification recommended a
      maximum of five redirections. Content developers should be aware
      that there might be clients that implement such a fixed
      limitation.

300 Multiple Choices

The requested resource corresponds to any one of a set of representations, each with its own specific location, and agent- driven negotiation information (section 12) is being provided so that the user (or user agent) can select a preferred representation and redirect its request to that location.
Unless it was a HEAD request, the response SHOULD include an entity containing a list of resource characteristics and location(s) from which the user or user agent can choose the one most appropriate. The entity format is specified by the media type given in the Content- Type header field. Depending upon the format and the capabilities of
the user agent, selection of the most appropriate choice MAY be performed automatically. However, this specification does not define any standard for such automatic selection.
If the server has a preferred choice of representation, it SHOULD include the specific URI for that representation in the Location field; user agents MAY use the Location field value for automatic redirection. This response is cacheable unless indicated otherwise.

301 Moved Permanently

The requested resource has been assigned a new permanent URI and any future references to this resource SHOULD use one of the returned URIs. Clients with link editing capabilities ought to automatically re-link references to the Request-URI to one or more of the new references returned by the server, where possible. This response is cacheable unless indicated otherwise.
The new permanent URI SHOULD be given by the Location field in the response. Unless the request method was HEAD, the entity of the response SHOULD contain a short hypertext note with a hyperlink to the new URI(s).
If the 301 status code is received in response to a request other than GET or HEAD, the user agent MUST NOT automatically redirect the request unless it can be confirmed by the user, since this might change the conditions under which the request was issued.

      Note: When automatically redirecting a POST request after
      receiving a 301 status code, some existing HTTP/1.0 user agents
      will erroneously change it into a GET request.

302 Found

The requested resource resides temporarily under a different URI. Since the redirection might be altered on occasion, the client SHOULD continue to use the Request-URI for future requests. This response is only cacheable if indicated by a Cache-Control or Expires header field.
The temporary URI SHOULD be given by the Location field in the response. Unless the request method was HEAD, the entity of the response SHOULD contain a short hypertext note with a hyperlink to the new URI(s).
If the 302 status code is received in response to a request other than GET or HEAD, the user agent MUST NOT automatically redirect the request unless it can be confirmed by the user, since this might change the conditions under which the request was issued.

      Note: RFC 1945 and RFC 2068 specify that the client is not allowed
      to change the method on the redirected request.  However, most
      existing user agent implementations treat 302 as if it were a 303
      response, performing a GET on the Location field-value regardless
      of the original request method. The status codes 303 and 307 have
      been added for servers that wish to make unambiguously clear which
      kind of reaction is expected of the client.

303 See Other

The response to the request can be found under a different URI and SHOULD be retrieved using a GET method on that resource. This method exists primarily to allow the output of a POST-activated script to redirect the user agent to a selected resource. The new URI is not a substitute reference for the originally requested resource. The 303 response MUST NOT be cached, but the response to the second (redirected) request might be cacheable.
The different URI SHOULD be given by the Location field in the response. Unless the request method was HEAD, the entity of the response SHOULD contain a short hypertext note with a hyperlink to the new URI(s).

      Note: Many pre-HTTP/1.1 user agents do not understand the 303
      status. When interoperability with such clients is a concern, the
      302 status code may be used instead, since most user agents react
      to a 302 response as described here for 303.

304 Not Modified

If the client has performed a conditional GET request and access is allowed, but the document has not been modified, the server SHOULD respond with this status code. The 304 response MUST NOT contain a message-body, and thus is always terminated by the first empty line after the header fields.
The response MUST include the following header fields:

      - Date, unless its omission is required by section 14.18.1

If a clockless origin server obeys these rules, and proxies and clients add their own Date to any response received without one (as already specified by [RFC 2068], caches will operate correctly.

      - ETag and/or Content-Location, if the header would have been sent
        in a 200 response to the same request

      - Expires, Cache-Control, and/or Vary, if the field-value might
        differ from that sent in any previous response for the same
        variant

If the conditional GET used a strong cache validator (see section 13.3.3), the response SHOULD NOT include other entity-headers. Otherwise (i.e., the conditional GET used a weak validator), the response MUST NOT include other entity-headers; this prevents inconsistencies between cached entity-bodies and updated headers.
If a 304 response indicates an entity not currently cached, then the cache MUST disregard the response and repeat the request without the conditional.
If a cache uses a received 304 response to update a cache entry, the cache MUST update the entry to reflect any new field values given in the response.

305 Use Proxy

The requested resource MUST be accessed through the proxy given by the Location field. The Location field gives the URI of the proxy. The recipient is expected to repeat this single request via the proxy. 305 responses MUST only be generated by origin servers.

      Note: RFC 2068 was not clear that 305 was intended to redirect a
      single request, and to be generated by origin servers only.  Not
      observing these limitations has significant security consequences.

306 (Unused)

The 306 status code was used in a previous version of the specification, is no longer used, and the code is reserved.

307 Temporary Redirect

The requested resource resides temporarily under a different URI. Since the redirection MAY be altered on occasion, the client SHOULD continue to use the Request-URI for future requests. This response is only cacheable if indicated by a Cache-Control or Expires header field.
The temporary URI SHOULD be given by the Location field in the response. Unless the request method was HEAD, the entity of the response SHOULD contain a short hypertext note with a hyperlink to the new URI(s) , since many pre-HTTP/1.1 user agents do not understand the 307 status. Therefore, the note SHOULD contain the information necessary for a user to repeat the original request on the new URI.
If the 307 status code is received in response to a request other than GET or HEAD, the user agent MUST NOT automatically redirect the request unless it can be confirmed by the user, since this might change the conditions under which the request was issued.

Client Error 4xx

The 4xx class of status code is intended for cases in which the client seems to have erred. Except when responding to a HEAD request, the server SHOULD include an entity containing an explanation of the error situation, and whether it is a temporary or permanent condition. These status codes are applicable to any request method. User agents SHOULD display any included entity to the user.
If the client is sending data, a server implementation using TCP SHOULD be careful to ensure that the client acknowledges receipt of the packet(s) containing the response, before the server closes the input connection. If the client continues sending data to the server after the close, the server's TCP stack will send a reset packet to the client, which may erase the client's unacknowledged input buffers before they can be read and interpreted by the HTTP application.

400 Bad Request

The request could not be understood by the server due to malformed syntax. The client SHOULD NOT repeat the request without modifications.

401 Unauthorized

The request requires user authentication. The response MUST include a WWW-Authenticate header field (section 14.47) containing a challenge applicable to the requested resource. The client MAY repeat the request with a suitable Authorization header field . If the request already included Authorization credentials, then the 401 response indicates that authorization has been refused for those credentials. If the 401 response contains the same challenge as the prior response, and the user agent has already attempted authentication at least once, then the user SHOULD be presented the entity that was given in the response, since that entity might include relevant diagnostic information. HTTP access authentication is explained in "HTTP Authentication: Basic and Digest Access Authentication".

402 Payment Required

This code is reserved for future use.

403 Forbidden

The server understood the request, but is refusing to fulfill it. Authorization will not help and the request SHOULD NOT be repeated. If the request method was not HEAD and the server wishes to make public why the request has not been fulfilled, it SHOULD describe the reason for the refusal in the entity. If the server does not wish to make this information available to the client, the status code 404 (Not Found) can be used instead.

404 Not Found

The server has not found anything matching the Request-URI. No indication is given of whether the condition is temporary or permanent. The 410 (Gone) status code SHOULD be used if the server knows, through some internally configurable mechanism, that an old resource is permanently unavailable and has no forwarding address. This status code is commonly used when the server does not wish to reveal exactly why the request has been refused, or when no other response is applicable.

405 Method Not Allowed

The method specified in the Request-Line is not allowed for the resource identified by the Request-URI. The response MUST include an Allow header containing a list of valid methods for the requested resource.

406 Not Acceptable

The resource identified by the request is only capable of generating response entities which have content characteristics not acceptable according to the accept headers sent in the request.
Unless it was a HEAD request, the response SHOULD include an entity containing a list of available entity characteristics and location(s) from which the user or user agent can choose the one most appropriate. The entity format is specified by the media type given in the Content-Type header field. Depending upon the format and the capabilities of the user agent, selection of the most appropriate choice MAY be performed automatically. However, this specification does not define any standard for such automatic selection.

      Note: HTTP/1.1 servers are allowed to return responses which are
      not acceptable according to the accept headers sent in the
      request. In some cases, this may even be preferable to sending a
      406 response. User agents are encouraged to inspect the headers of
      an incoming response to determine if it is acceptable.

If the response could be unacceptable, a user agent SHOULD temporarily stop receipt of more data and query the user for a decision on further actions.

407 Proxy Authentication Required

This code is similar to 401 (Unauthorized), but indicates that the client must first authenticate itself with the proxy. The proxy MUST return a Proxy-Authenticate header field  containing a challenge applicable to the proxy for the requested resource. The client MAY repeat the request with a suitable Proxy-Authorization header field . HTTP access authentication is explained in "HTTP Authentication: Basic and Digest Access Authentication".

408 Request Timeout

The client did not produce a request within the time that the server was prepared to wait. The client MAY repeat the request without modifications at any later time.

409 Conflict

The request could not be completed due to a conflict with the current state of the resource. This code is only allowed in situations where it is expected that the user might be able to resolve the conflict and resubmit the request. The response body SHOULD include enough
information for the user to recognize the source of the conflict. Ideally, the response entity would include enough information for the user or user agent to fix the problem; however, that might not be possible and is not required.
Conflicts are most likely to occur in response to a PUT request. For example, if versioning were being used and the entity being PUT included changes to a resource which conflict with those made by an earlier (third-party) request, the server might use the 409 response to indicate that it can't complete the request. In this case, the response entity would likely contain a list of the differences between the two versions in a format defined by the response Content-Type.

410 Gone

The requested resource is no longer available at the server and no forwarding address is known. This condition is expected to be considered permanent. Clients with link editing capabilities SHOULD delete references to the Request-URI after user approval. If the server does not know, or has no facility to determine, whether or not the condition is permanent, the status code 404 (Not Found) SHOULD be used instead. This response is cacheable unless indicated otherwise.
The 410 response is primarily intended to assist the task of web maintenance by notifying the recipient that the resource is intentionally unavailable and that the server owners desire that remote links to that resource be removed. Such an event is common for limited-time, promotional services and for resources belonging to individuals no longer working at the server's site. It is not necessary to mark all permanently unavailable resources as "gone" or to keep the mark for any length of time -- that is left to the discretion of the server owner.

411 Length Required

The server refuses to accept the request without a defined Content- Length. The client MAY repeat the request if it adds a valid Content-Length header field containing the length of the message-body in the request message.

412 Precondition Failed

The precondition given in one or more of the request-header fields evaluated to false when it was tested on the server. This response code allows the client to place preconditions on the current resource metainformation (header field data) and thus prevent the requested method from being applied to a resource other than the one intended.

413 Request Entity Too Large

The server is refusing to process a request because the request entity is larger than the server is willing or able to process. The server MAY close the connection to prevent the client from continuing the request.
If the condition is temporary, the server SHOULD include a Retry- After header field to indicate that it is temporary and after what time the client MAY try again.

414 Request-URI Too Long

The server is refusing to service the request because the Request-URI is longer than the server is willing to interpret. This rare condition is only likely to occur when a client has improperly converted a POST request to a GET request with long query information, when the client has descended into a URI "black hole" of redirection (e.g., a redirected URI prefix that points to a suffix of itself), or when the server is under attack by a client attempting to exploit security holes present in some servers using fixed-length buffers for reading or manipulating the Request-URI.

415 Unsupported Media Type

The server is refusing to service the request because the entity of the request is in a format not supported by the requested resource for the requested method.

416 Requested Range Not Satisfiable

A server SHOULD return a response with this status code if a request included a Range request-header field (section 14.35), and none of the range-specifier values in this field overlap the current extent of the selected resource, and the request did not include an If-Range request-header field. (For byte-ranges, this means that the first- byte-pos of all of the byte-range-spec values were greater than the current length of the selected resource.)
When this status code is returned for a byte-range request, the response SHOULD include a Content-Range entity-header field specifying the current length of the selected resource. This response MUST NOT use the multipart/byteranges content- type.

417 Expectation Failed

The expectation given in an Expect request-header field (see section 14.20) could not be met by this server, or, if the server is a proxy, the server has unambiguous evidence that the request could not be met by the next-hop server.

Server Error 5xx

Response status codes beginning with the digit "5" indicate cases in which the server is aware that it has erred or is incapable of performing the request. Except when responding to a HEAD request, the server SHOULD include an entity containing an explanation of the error situation, and whether it is a temporary or permanent condition. User agents SHOULD display any included entity to the user. These response codes are applicable to any request method.

500 Internal Server Error

The server encountered an unexpected condition which prevented it from fulfilling the request.

501 Not Implemented

The server does not support the functionality required to fulfill the request. This is the appropriate response when the server does not recognize the request method and is not capable of supporting it for any resource.

502 Bad Gateway

The server, while acting as a gateway or proxy, received an invalid response from the upstream server it accessed in attempting to fulfill the request.

503 Service Unavailable

The server is currently unable to handle the request due to a temporary overloading or maintenance of the server. The implication is that this is a temporary condition which will be alleviated after some delay. If known, the length of the delay MAY be indicated in a Retry-After header. If no Retry-After is given, the client SHOULD handle the response as it would for a 500 response.

      Note: The existence of the 503 status code does not imply that a
      server must use it when becoming overloaded. Some servers may wish
      to simply refuse the connection.

504 Gateway Timeout

The server, while acting as a gateway or proxy, did not receive a timely response from the upstream server specified by the URI (e.g. HTTP, FTP, LDAP) or some other auxiliary server (e.g. DNS) it needed to access in attempting to complete the request.

      Note: Note to implementors: some deployed proxies are known to
      return 400 or 500 when DNS lookups time out.

505 HTTP Version Not Supported

The server does not support, or refuses to support, the HTTP protocol version that was used in the request message. The server is indicating that it is unable or unwilling to complete the request using the same major version as the client, as described in section, other than with this error message. The response SHOULD contain an entity describing why that version is not supported and what other protocols are supported by that server.

Source

Penjelasan tentang HTTP Request Method (GET, HEAD, POST, PUT, DELETE, OPTIONS, TRACE)

Topik-topik pengantar berikut akan dibahas dalam artikel ini:
Siklus hidup dari permintaan HTTP & respon.
Anatomi permintaan HTTP & respon.
HTTP Metode & praktik terbaik.

Gambar 1: HTTP Request / Response

Siklus hidup dari permintaan HTTP umumnya terlihat seperti ini:

1. Seorang pengguna mengunjungi URL dari sebuah situs web.
2. Hal ini menciptakan permintaan yang diarahkan ke web server melalui internet (jaringan DNS itu, router dan switch) melalui HTTP (Hypertext Transfer Protocol).
3. Web server menerima permintaan HTTP dan merespon pengguna dengan halaman web (atau isi) yang diminta.

Setiap kali Anda mengklik link dan mengunjungi halaman web, di belakang layar Anda membuat permintaan, dan pada gilirannya menerima respon dari web server. Perhatikan bahwa permintaan HTTP dapat dilakukan melalui banyak saluran, bukan hanya web browser. Misalnya, permintaan HTTP dapat dibuat dengan menggunakan TELNET, atau klien ditulis dalam JAVA atau C # dll

Untuk melihat contoh dari apa yang permintaan HTTP dan respon sepertinya melakukan hal berikut:

1. Pergi ke situs http://web-sniffer.net/
2. Ketik www.google.com (atau situs web apapun yang Anda inginkan) pada "HTTP (S)-URL:" field input. Ketika Anda klik "Submit" Anda akan melihat permintaan HTTP dan data respon untuk www.google.com.

Anatomi permintaan HTTP:
Sebagai web developer, daerah penting untuk dipahami adalah bagian metode permintaan HTTP. Metode ini memberitahu server web apa permintaan sedang dilakukan pada URI.
Jadi jika Anda mengetikkan URL www.google.com / keuangan (misalnya). Anda meminta URI / keuangan. Dalam URI / keuangan permintaan HTTP harus menentukan metode HTTP.

Metode porsi permintaan HTTP berisi opsi definisi sebagai berikut:

Method         = "OPTIONS"
                      | "GET"
                      | "HEAD"
                      | "POST"
                      | "PUT"
                      | "DELETE"
                      | "TRACE"
                      | "CONNECT"
                      | extension-method
       extension-method = token

OPTION
Pilihan ini berguna untuk mencari tahu mana metode HTTP dapat diakses oleh klien.Tergantung pada bagaimana web server Anda mencoba untuk menyambung ke dikonfigurasi, administrator mungkin hanya memiliki POST dan GET metode HTTP diakses. Sementara metode HTTP lain seperti DELETE, TRACE, dll dinonaktifkan.

GET
Sebuah permintaan GET mengambil data dari web server dengan menentukan parameter di bagian URL dari permintaan. Jika Anda memeriksa contoh permintaan HTTP bawah ini, kami minta index.html, dan melewati report_id parameter.

GET /index.html?report_id=34543222 HTTP/1.1
 Host: www.awebsite.com
 User-Agent: Safari/4.0

Contoh saat menggunakan GET:

1. Anda mengakses URL murni demi melihat data. Anda bisa menganggapnya sebagai menggunakan pernyataan SELECT SQL. Anda meminta data dari server web tanpa maksud memperbarui data apapun.
2. Anda perlu URL untuk menjadi 'bookmarkable'. Pada dasarnya HTTP GET dianggap diulangi, yang memungkinkan permintaan untuk dicoba aman dan tanggapan-cache.
3. Anda tidak keberatan permintaan diulang. Misalnya pengguna mengunjungi URL yang sama lebih dari sekali.

Contoh ketika tidak menggunakan GET:

1. Anda lewat data sensitif seperti username, password, nomor jaminan sosial, dll
2. Anda mengirimkan data dalam jumlah besar. Meskipun tidak ada batas karakter didefinisikan dalam spesifikasi HTTP untuk panjang URL, IE 4 misalnya hanya mendukung URL panjang maksimum ~ 2000 karakter menggunakan permintaan GET.
3. Anda perlu memperbarui sesuatu pada server, misalnya mengirimkan formulir yang akan memperbarui alamat pengguna atau keranjang belanja.

POST
Sebuah permintaan HTTP POST memanfaatkan badan pesan untuk mengirim data ke server web. Jika Anda memeriksa contoh permintaan HTTP POST di bawah ini, Anda akan melihat bahwa kita mengirimkan permintaan HTTP POST dengan tubuh pesan 'userid = mo & password = mypassw' untuk login.jsp (login.jsp akan menjadi sebuah aplikasi yang ke depan server web permintaan untuk).
Contoh saat menggunakan POST:

1. Anda memiliki sejumlah besar data untuk mengirim ke server web (ukuran data akan melebihi batas URL dari metode GET).
2. Anda mengirim data sensitif seperti uesrnames, password, nomor jaminan sosial dan lain-lain
3. Anda mengubah keadaan data dalam aplikasi web. Misalnya, keranjang belanja melacak item yang Anda beli.

Contoh ketika tidak menggunakan POST:

1. URL yang Anda melewati memiliki persyaratan menjadi 'bookmarkable'. Jika keadaan perubahan URL, maka pengguna tidak akan dapat mengambil, atau melihat data itu itu adalah mantan negara.
2. Permintaan Anda perlu idempotent. Perhatikan bahwa permintaan POST bisa idempotent, namun itu praktik yang lebih baik untuk menggunakan PUT (jika metode permintaan HTTP ini didukung oleh web server dan client) 

POST /login.jsp HTTP/1.1
 Host: www.awebsite.com
 User-Agent: Safari/4.0
 Content-Length: 27
 Content-Type: application/x-www-form-urlencoded

 userid=mo&password=mypassw

PUT
PUT mirip dengan POST memanfaatkan badan pesan untuk mentransfer data. Namun, ada beberapa perbedaan mendasar antara keduanya. Pertama PUT dianggap idempotent, kedua tindakan seorang PUT ini selalu ditetapkan untuk URI tertentu, akhirnya PUT adalah untuk memuat data untuk sumber daya itu. Dengan kata lain Anda harus tahu lokasi yang tepat dari mana data yang Anda kirimkan akan diambil nanti.
Contoh kapan harus menggunakan PUT:

1. Masukan adalah idempotent, jadi pada dasarnya jika Anda perlu untuk mengakomodasi untuk skenario di mana ada permintaan yang disampaikan beberapa kali tapi hasilnya harus sama untuk setiap pengiriman, penggunaan PUT.Ini bisa berguna untuk membuat user baru misalnya. Jika Anda mengirim permintaan PUT untuk membuat user Joe Smith beberapa kali, permintaan terakhir harus memiliki hasil yang sama seolah-olah dikirim pertama.
2. Anda memiliki URI khusus yang Anda mengirim data ke. Sebagai contoh:

POST URI:

 http://hostname.com/users/new

 PUT URI:

 http://hostname.com/users/privacyyou

Contoh ketika tidak menggunakan PUT:

1. PUT tidak boleh digunakan untuk permintaan non idempotent (jika keadaan sumber daya kemungkinan akan berubah setiap kali permintaan dikirim).
2. Ada baiknya untuk diingat bahwa dalam kasus bentuk html, kebanyakan browser tidak mendukung PUT / DELETE metode. Diharapkan POST / GET digunakan.Beberapa kerangka Tenang seperti Ruby on Rails misalnya memerlukan penggunaan PUT / DELETE, namun ini Metode HTTP hanya terowongan melalui Metode POST HTTP. 

PUT /somedatabase/some_doc_id HTTP/1.1
 Content-Length: 240
 Content-Type: application/json

 {
   "Subject":"Resume",
   "Author":"Mo",
   "Body":"Find my resume attached"
 }

HEAD
HTTP Metode HEADgunakan untuk mengambil informasi tentang URL dari web server. Jadi misalnya jika Anda mengirim permintaan HEAD, Anda akan menerima respon dari server web yang berisi informasi yang sama seperti yang Anda lakukan dengan HTTP POST tidak termasuk data tubuh. Berikut adalah contoh:

HEAD /de HTTP/1.1[CRLF]
 Host: www.google.com[CRLF]
 Connection: close[CRLF]
 User-Agent: Web-sniffer/1.0.37 [CRLF]
 Accept-Encoding: gzip[CRLF]
 Accept-Charset: ISO-8859-1,UTF-8;q=0.7,*;q=0.7[CRLF]
 Cache-Control: no-cache[CRLF]
 Accept-Language: de,en;q=0.7,en-us;q=0.3[CRLF]
 Referer: http://web-sniffer.net/[CRLF]

DELETE
Metode HTTP DELETE dapat digunakan untuk menghapus sumber daya dari server.Umumnya digunakan dalam dua skenario. Skenario Fist adalah jika Anda mengikuti standar tenang dalam mengembangkan aplikasi web Anda. Kedua hal itu dapat digunakan saat DELETE diaktifkan pada web-server dan Anda ingin mengikuti standar HTTP untuk menghapus sumber daya. Sangat penting untuk dicatat namun yang dapat Anda gunakan HTTP POST untuk menangani tindakan HTTP DELETE juga, keputusan dipersempit ke opsi yang diuraikan di atas.


TRACE
Jika Anda mencoba untuk menjalankan metode TRACE HTTP pada kebanyakan web server-Anda mungkin akan melihat pesan ini: 

Status: HTTP/1.1 501 Not Implemented

HTTP TRACE digunakan untuk eacho isi dari Permintaan HTTP kembali ke pemohon (yang dapat berguna untuk debugging). Namun ini dapat menimbulkan ancaman keamanan karena kode berbahaya dapat menyalahgunakan fungsi TRACE HTTP untuk mendapatkan akses ke informasi dalam header HTTP seperti cookies dan data otentikasi, jika permintaan TRACE HTTP dikirim data permohonan asli akan dikembalikan di samping setiap pengguna tertentu data. Contoh respon HTTP TRACE dapat terlihat seperti ini: 

TRACE / HTTP/1.1
 Host: www.google.com

 HTTP/1.1 200 OK
 Server: Microsoft-IIS/5.0
 Date: Tue, 31 Oct 2012 03:01:44 GMT
 Connection: close
 Content-Type: message/http
 Content-Length: 39

 TRACE / HTTP/1.1
 Host: www.google.com

CONNECT
HTTP CONNECT dapat digunakan untuk membuat sambungan jaringan ke server web melalui HTTP. Ini terutama digunakan dalam kasus di mana sebuah koneksi HTTP aman / terenkripsi (terowongan) perlu dibangun antara klien dan web server seperti koneksi SSL.
Terowongan HTTP sederhana koneksi terenkripsi melalui proxy HTTP untuk tujuan sewenang-wenang. Terowongan mengambil keuntungan dari metode HTTP CONNECT biasanya digunakan untuk HTTPS (lalu lintas web yang aman) untuk menghubungkan ke server tujuan. Sebuah koneksi HTTPS khas melalui proxy akan terlihat seperti: 

CONNECT remote-server:443 HTTP/1.0
 User-Agent: Mozilla/4.0 (compatible; MSIE 6.0;..
 Host: remote-server
 Content-Length: 0
 Proxy-Connection: Keep-Alive
 Pragma: no-cach

Respon HTTP Codes
Setiap kali permintaan dibuat ke server HTTP, kode respon dikirim kembali ke klien yang menyertai data yang diminta. Sangat penting untuk memahami apa kode respon adalah sebagai mereka akan berguna untuk mengelola kesalahan dalam aplikasi web Anda.

Source

Pengertian dan List URL Encoding

Postingan kali ini saya akan coba untuk menjelaskan tentang apa itu URL encoding, mungkin banyak yang belum tahu atau belum pernah sama sekali mendengar kata “URL encoding”, tapi percayalah jika anda seorang gretongerz anda mungkin pernah menggunakan URL encoding yang akan saya jelaskan ini

URL encoding adalah proses konversi URL (Uniform Resource Locator) saat kita melakukan proses request suatu halaman situs ke web server. Kenapa URL harus di konversi dahulu sebelum browser melakukan request ke web server ? karena sering kali kita menjumpai URL yang tidak termasuk atau di luar standar ASCII dan juga URL tidak boleh mengandung “spasi”, nah loh..? ASCII apa lagi ini ?  :-O

ASCII adalah karakter yang digunakan saat kita mengirim atau menerima informasi ataupun data antar komputer. ASCII merupakan standar yang sudah ditetapkan untuk karakter yang digunakan untuk saling bertukar informasi sejak awal tahun 60′an dan masih digunakan sampai sekarang.
Nah, untuk itu saat kita akan mengakses suatu situs ataupun blog, secara otomatis browser kita akan melakukan yang kita sebut “URL encoding” untuk menghindari spasi dan juga terdapatnya karekter yang tidak termasuk dalam ASCII dalam suatu URL.

Saya akan memberikan satu contoh, berikut ini contoh URL sebelum di encode oleh browser, URL yang biasa kita gunakan sehari – hari untuk mengakses suatu halaman.

http://www.facebook.com/Privacyyou
Saat browser akan melakukan request, browser akan men-konversi terlebih dulu URL tersebut menjadi.

http%3A%2F%2Fwww.facebook.com%2FPrivacyyou
Saya yakin untuk gretongerz sejati, URL diatas sudah tidak asing lagi  :-D , konversi karakter ini selalu diawali dengan karekter % dan diikuti dua digit hexadesimal.
Contoh untuk karekter “/” dikonversi menjadi “%2F” begitu juga dengan karakter lainnya, tentunya dengan dua digit hexadesimal yang berbeda

Untuk karakter – karekter lainnya bisa di lihat disini, disitu anda juga bisa mencoba generate URL biasa menjadi URL encoding secara instant, dengan hanya copy paste URL yang akan anda coba lalu klik submit.

berikut LIST Url Encoding yang bisa anda lihat di http://www.w3schools.com/tags/ref_urlencode.asp


Mudah – mudahan bisa berguna
Mohon ditambahkan jika masih ada yang kurang atau jika ada kesalahan jangan sungkan untuk komentar di form komentar di bawah.

Source

Cara Download Indowebster (Lokal) Menggunakan SSH (C2S Forwarding)

Sering kali kita menggunakan SSH terutama dengan Internet Gratisan. Pada kesempatan ini saya akan Share Cara Download Indowebster (Lokal) Menggunakan SSH menggunakan fitur bawaan dari bitvise. Oke Let's Go

1. Seperti biasa kita buka Bitvise, lalu klik C2S

2. Klik Add

3. Isi Proxy seperti gambar di bawah ini , lalu klik login

NB: Untuk Destination Host dan Dest Port sesuaikan dengan Proxy dan Port yang kalian Punya

untuk mendapatkan proxy, anda bisa cek di postingan saya yang ini Click Here

4. Jika muncul log seperti ini, itu berarti anda telah sukses menggunakan C2S Forwarding

5. Setting Proxy di Browser, di gambar ini saya menggunakan Google chrome

6. Kita Cek IP kita di 123myip.co.uk jika IP yang muncul sama dengan proxy yang kita isi di C2S Bitvise tadi, berarti kita telah sukses, dan siap mendownload file dari Indowebster :D

Selamat Mencoba

VPN dan Proxy Server

Virtual Private Network (VPN) dan Proxy Server memiliki tujuan penggunaan yang sama namun dengan fungsi yang berbeda satu sama lain. Baik VPN maupun proxy server mempunyai kecepatan, kestabilan dan keamanan yang ditentukan berdasarkan harga (gratis dan berbayar). Meskipun banyak anggapan keduanya sama, namun dari segi cara kerja sudah jelas koneksi proxy server dan VPN berbeda.

Meskipun memiliki perbedaan fungsi dan cara kerja, VPN dan proxy server memiliki manfaat yang sama yaitu menyembunyikan identitas alamat IP asli dari komputer maupun perangkat lain yang digunakan.

Virtual Private Network (VPN):

Virtual Private Network akan membangun koneksi terenkripsi antara komputer dengan server host VPN, dimana setiap traffic internet melewati server host VPN. Dengan enkripsi minimal 128-bit, VPN dapat mengamankan data yang di kirim maupun diterima komputer yang anda gunakan. Selain IP Address berubah, menggunakan server VPN seakan-akan sedang memakai ISP lain.

Semua traffic akan melewati server VPN sehingga aktivitas komputer, alamat situs web yang anda kunjungi, dan lainnya, benar-benar tidak terlihat oleh pihak manapun. VPN juga mendukung High Levels Encryption dari 128-bit sampai 2048-bit.

Melalui jaringan Virtual Private Network, anda dapat mengirim dan menerima file dari komputer satu ke komputer lain yang juga terhubung ke server VPN. Dimana kecepatan, keamanan dan kestabilan yang berbading lurus dengan harga layanan yang harus anda bayar.

Tidak hanya server luar negeri saja, provider VPN Indonesia sudah banyak bermunculan sehingga memudahkan anda dalam menggunakan koneksi aman melalui VPN.

Untuk dapat menggunakan server VPN, dibutuhkan sedikit keterampilan dalam mendownload VPN Client, melakukan setting dan konfigurasi antara perangkat komputer dengan server host VPN.

Proxy Server:

Proxy merupakan komputer server yang bertindak sebagai perantara antara komputer yang anda gunakan dengan internet. Tidak seperti VPN, proxy server tidak selalu melakukan enkripsi data yang dikirim maupun diterima komputer melalui jaringan internet.

Saat anda menggunakan proxy server, IP address yang terlihat adalah IP proxy yang dimiliki komputer perantara tersebut, bukan IP komputer yang sedang anda pakai. Banyak software proxy yang memberikan kemudahan untuk memakai IP proxy dari komputer lain, salah satunya adalah Ultrasurf

Ada 2 jenis protokol yang umum digunakan oleh proxy server:

• HTTP Proxy Server: protokol HTTP digunakan untuk mengakses traffic tingkat HTTP seperti http:// atau https:// yang artinya hanya dapat untuk membuka halaman web. Untuk sekedar browsing di internet, HTTP proxy lebih cepat bila dibandingkan Sock proxy server.
• SOCKS Proxy Server: sock proxy memiliki kemampuan lebih komplit dibandingkan HTTP proxy, selain dapat digunakan untuk mengakses halaman situs web, Sock proxy server dapat membuka POP3 dan SMPT untuk email, IRC chat, FTP untuk upload file ke situs web serta torrent file.

Kesimpulan:

VPN lebih unggul di segala bidang mulai dari sisi keamanan, kecepatan akses serta kestabilan koneksi server. Virtual Private Network mampu melindungi sepenuhnya (secure) semua aktivitas online yang anda kerjakan bahkan tidak terlihat oleh pihak ISP (Internet Services Provider)

Source