1. Welcome to PHCorner Forums. Take a moment to Sign up and gain unlimited access and extra privileges that guests are not entitled to, such as:

    All that and more! Registration is quick, simple and absolutely free. Join our community today!

Help Status 403 sino po may alam

Discussion in 'Smart, TNT & Sun Questions' started by spitfire05, Aug 9, 2016.

  1. spitfire05

    spitfire05 Grasshopper Established

    paturo po paano status 403 sa http injector wala po akong mahanap dito na tutorial
     
  2. status 403 is forbidden, not suitable for your connection.
     
  3. spitfire05

    spitfire05 Grasshopper Established

    yan po gamit ko na napulot ko lang sa fb mabilis siya kaysa status 200 ok
     
  4. kapag forbidden kasi di gumagana sakin.. maybe payload or remote proxy ang may mali
     
  5. spitfire05

    spitfire05 Grasshopper Established

    eto po log niya
    [2016-08-09 12:15:11] Running on HUAWEI CHM-U01 (BalongV8R1SFT) Honor, Android API 19
    [2016-08-09 12:15:11] Application version: 3.1.0 Build 50
    [2016-08-09 12:15:32] <strong>Using VPN Service</strong>
    [2016-08-09 12:15:32] [START] service requested
    [2016-08-09 12:15:34] Injector Service Started
    [2016-08-09 12:15:34] Network Status: CONNECTED HSPA to mobile internet
    [2016-08-09 12:15:34] Acquire wakelock
    [2016-08-09 12:15:34] Local IP: 100.97.213.241
    [2016-08-09 12:15:34] Starting listening local port: <b>8989</b>
    [2016-08-09 12:15:34] Starting - Network Task
    [2016-08-09 12:15:34] Listening for incoming connection
    [2016-08-09 12:15:34] Start tunnel service
    [2016-08-09 12:15:43] Buffer Size: 32767
    [2016-08-09 12:15:43] Running - Proxy Thread
    [2016-08-09 12:15:43] Running - Proxy Thread
    [2016-08-09 12:15:43] Injecting
    [2016-08-09 12:15:44] <strong>Status: 403 (Forbidden)</strong> Client Error - The client seems to have erred.
    [2016-08-09 12:15:44] <strong>Extra Info</strong> Please make sure remote proxy allow your access/request method.
    [2016-08-09 12:15:44] Sending 200 HTTP status - HTTP/1.1 200 OK


    [2016-08-09 12:15:51] Authenticate with password
    [2016-08-09 12:15:52] Forward Successful
    [2016-08-09 12:15:52] <strong>Connected</strong>
    [2016-08-09 12:15:52] Starting Injector VPN Service
    [2016-08-09 12:15:52] Google DNS enabled
    [2016-08-09 12:15:52] DNS forwarding enabled
    [2016-08-09 12:15:52] Tunnel core started
    [2016-08-09 12:16:32] Start tunnel service
    [2016-08-09 12:16:32] IOException: recvfrom failed: ECONNRESET (Connection reset by peer)
    [2016-08-09 12:16:32] Finally - Closing connection
    [2016-08-09 12:16:32] IOException: Socket closed
    [2016-08-09 12:16:32] Connection Lost
    [2016-08-09 12:16:32] Tunnel: waiting connection
    [2016-08-09 12:16:32] Buffer Size: 32767
    [2016-08-09 12:16:32] Running - Proxy Thread
    [2016-08-09 12:16:32] Running - Proxy Thread
    [2016-08-09 12:16:32] Injecting
    [2016-08-09 12:16:33] <strong>Status: 403 (Forbidden)</strong> Client Error - The client seems to have erred.
    [2016-08-09 12:16:33] <strong>Extra Info</strong> Please make sure remote proxy allow your access/request method.
    [2016-08-09 12:16:33] Sending 200 HTTP status - HTTP/1.1 200 OK


    [2016-08-09 12:16:34] Authenticate with password
    [2016-08-09 12:16:35] Forward Successful
    [2016-08-09 12:16:36] <strong>Connected</strong>
    [2016-08-09 12:19:49] Start tunnel service
    [2016-08-09 12:19:49] IOException: recvfrom failed: ECONNRESET (Connection reset by peer)
    [2016-08-09 12:19:49] Finally - Closing connection
    [2016-08-09 12:19:49] Connection Lost
    [2016-08-09 12:19:49] IOException: Socket closed
    [2016-08-09 12:19:49] Tunnel: waiting connection
    [2016-08-09 12:19:49] Buffer Size: 32767
    [2016-08-09 12:19:49] Running - Proxy Thread
    [2016-08-09 12:19:49] Running - Proxy Thread
    [2016-08-09 12:19:50] Injecting
    [2016-08-09 12:19:50] <strong>Status: 403 (Forbidden)</strong> Client Error - The client seems to have erred.
    [2016-08-09 12:19:50] <strong>Extra Info</strong> Please make sure remote proxy allow your access/request method.
    [2016-08-09 12:19:50] Sending 200 HTTP status - HTTP/1.1 200 OK


    [2016-08-09 12:19:52] Authenticate with password
    [2016-08-09 12:19:53] Forward Successful
    [2016-08-09 12:19:53] <strong>Connected</strong>
     
  6. hanneman

    hanneman Eternal Poster Established

    private access yan valid yung request but you need the right permissions...
     
  7. ayus napagana mo, ako di pa nakakapag pagana ng 403 , mabilis kasi ma (dc) pag 201 pataas..
     
  8. spitfire05

    spitfire05 Grasshopper Established

    hindi sir yan yun napulot kong ehi sa fb hehe tinaning ko po yung gumawa ayaw naman mag reply hehe
     
  9. vifer

    vifer Addict Established

    e2 po ibig sabihin ng response
    kapag ayaw magconnect. taz 200k pero close connection. ky silipin nyo din kung open o close






    HTTP RESPONSE CODES:
    100 Continue
    The server has not rejected the initial part of the request, and the client should continue.
    101 Switching Protocols
    The server agrees with the client's request to change protocols.
    200 OK
    The request has succeeded.
    201 Created
    The request has been fulfilled and resulted in a new resource being created.
    202 Accepted
    The request has been accepted for processing, but the processing has not been completed.
    203 Non-Authoritative Information
    The returned headers are not definitive, but are gathered from a local or a third-party copy.
    204 No Content
    The server has fulfilled the request but does not need to return any output.
    205 Reset Content
    The server has fulfilled the request and the client should reset the document view (primarily intended to make data-entry easier).
    206 Partial Content
    The server has fulfilled the partial GET request for the resource.
    300 Multiple Choices
    There are several resources that match this request, and the client was redirected to one of them.
    301 Moved Permanently
    The requested resource has been assigned a new permanent URI and any future references to this resource should use the new URI.
    302 Found
    The requested resource resides temporarily under a different URI. Since the redirection might be altered, continue to use the old URI.
    303 See Other
    The response to the request can be found under a different URI and should be retrieved from the new URI.
    304 Not Modified
    The document has not been modified since the last request, and the locally cached copy should be used instead.
    305 Use Proxy
    The requested resource must be accessed through a proxy.
    306 (Unused)
    Used in a previous version of the protocol.
    307 Temporary Redirect
    The requested resource resides temporarily under a different URI. Since the redirection may be altered on occasion, continue to use the current URI.
    400 Bad Request
    The request could not be understood by the server due to malformed syntax.
    401 Unauthorized
    The request requires user authentication.
    402 Payment Required
    This code is reserved for future use.
    403 Forbidden
    The server understood the request, but is refusing to fulfill it. Typically due to file access permissions on the server.
    404 Not Found
    The server has not found anything matching the URI.
    405 Method Not Allowed
    The request method is not allowed. Typically when trying to execute a normal document or display a script.
    406 Not Acceptable
    According to the client's request, it isn't capable of handling the response.
    407 Proxy Authentication Required
    This code is similar to 401 (Unauthorized), but indicates that the client must first authenticate itself with the proxy.
    408 Request Timeout
    The client did not produce a request within the time that the server was prepared to wait.
    409 Conflict
    The request could not be completed due to a conflict with the current state of the resource. Typically only seen with clients that can manage files on the remote server.
    410 Gone
    The requested resource is no longer available at the server and no forwarding address is known.
    411 Length Required
    The server refuses to accept the request without a defined Content-Length header.
    412 Precondition Failed
    The precondition given in one or more of the header fields failed when it was tested on the server.
    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.
    414 Request-URI Too Long
    The server is refusing to service the request because the requested URI is too long.
    415 Unsupported Media Type
    The server is refusing to service the request because the client does not support the response format.
    416 Requested Range Not Satisfiable
    The server could not find the range specified in the Range header.
    417 Expectation Failed
    The server could not meet the expectation given in the Expect header.
    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.
    502 Bad Gateway
    The server is a gateway or proxy and 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.
    504 Gateway Timeout
    The server is a gateway or proxy and did not receive a timely response from the upstream server.
    505 HTTP Version Not Supported
    The server does not support, or refuses to support, the HTTP protocol version that was used in the request.
    600 Malformed URI
    The link checking program was not able to parse the URI. This means that the URI was either empty, or not a valid URI (e.g. "Ask at S&E Reference Desk").
    601 Connection Timed Out
    The server did not respond before the connection timed out.
    602 Unknown Error
    Some other error occurred in contacting the server, making the request, or parsing the response. This could be due to a mangled or incorrectly formatted response from the server.
    603 Could Not Parse Reply
    The reply from the server could not be parsed. This could indicate a malformed response, or a non-numerical response code.
    604 Protocol Not Supported
    This URI uses a protocol that is not currently supported by the linkchecker program. The linkchecker currently only supports http, so ftp, https, gopher, etc. are not supported. Also, some protocols (such as mailto://) cannot be checked
     
    hanneman likes this.
  10. remote proxy niya ay mabilis ang speed! yung mabibilis na proxy ay madali madc at mabilis makatay.
     
  11. spitfire05

    spitfire05 Grasshopper Established

    sir tanong ko lang bakit kaya port 3138 8888 60000 lang mapagakana kong remote proxy
     
  12. squid proxy kasi sila!
     
    spitfire05 likes this.
  13. jpricacho27

    jpricacho27 Enthusiast Established

    either hindi supported ng proxy ang ports or ssl, try to change port from 22 to 443.
     
  14. 403 connected... bag0 yan ^^
     
  15. sappia

    sappia Grasshopper Established

    Pahingi po setting ng 403
     
Tags / Keywords: