[Autokill-Hit-HP] GMVP Trainer ELite GCNA(usa) Chaos v4.0 17-08-11

08/27/2011 05:38 Tactickz#121
So we were never allowed to use this hack since the Forbidden Page error?

My apologies.
08/27/2011 05:42 XxJoshuaEvansxX#122
LOL Before its a 403 error now its a HTTP 302 error..
08/27/2011 05:51 tsuna93#123
omg...HTTP/1.1 302 found
what is this

so now this hack doesnt work now
keep pop out the error
HTTP/1.1 302 found
08/27/2011 08:18 fainaka#124
the error also eat my IE homepage after open it.... it eat my homepage then the homepage change to another website
08/27/2011 09:33 Bashtion#125
Trainer doesn't work now , 'cause GC updated
08/28/2011 00:55 Santaday#126
I'm guessing no one right now knows how to fix the http/1.1 302 found error.......
08/28/2011 02:12 Trob#127
it says HTTP/ 1.1 302 Found. Then i cant click anything ? Any fix ?
08/28/2011 04:28 gongbazhongshen#128
302means the main page has been deleted......
so thay dont want to run this any more
we need some one can Completely revise like delete the connection or make it run from the part after Advertisement
08/28/2011 08:31 branj13#129
but even if you make it "offline" the addresses needed for memory hacking will be rendered useless after a maintenance (some may remain unchanged but expect for the important functions to change) for it to function as it supposed to work, unless if someone is skilled as miguel to make a trainer that uses memory hacking but as far as I know, miguel is the only one who's making (and release) these kinds of trainers, the other ones sprouting here in epvp mimicking miguel's releases is a certified leecher from other sites (to be precise the one who tries to release BR trainers via memory hacking, miguel usually releases NAGC trainers and GCPH trainers sometimes)...
08/28/2011 19:30 Santaday#130
Quote:
Originally Posted by branj13 View Post
but even if you make it "offline" the addresses needed for memory hacking will be rendered useless after a maintenance (some may remain unchanged but expect for the important functions to change) for it to function as it supposed to work, unless if someone is skilled as miguel to make a trainer that uses memory hacking but as far as I know, miguel is the only one who's making (and release) these kinds of trainers, the other ones sprouting here in epvp mimicking miguel's releases is a certified leecher from other sites (to be precise the one who tries to release BR trainers via memory hacking, miguel usually releases NAGC trainers and GCPH trainers sometimes)...
ok i got lost after the first 10 words........
08/28/2011 22:07 Sasuke39#131
Eek Http error that sucks i've been using this since friday and for the 403 error just just another website that has a banner...
08/29/2011 20:30 elvy93#132
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.

Quoted from: [Only registered and activated users can see links. Click Here To Register...]
08/29/2011 22:16 Santaday#133
Quote:
Originally Posted by elvy93 View Post
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.

Quoted from: [Only registered and activated users can see links. Click Here To Register...]
Again....i got lost in after the first 10 words........

im so stupid.....:(
08/30/2011 11:15 ly9577#134
Quote:
Originally Posted by elvy93 View Post
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.

Quoted from: [Only registered and activated users can see links. Click Here To Register...]

thanks, but any words can deal with the problem, BTW.
08/31/2011 07:55 junuxhuck#135
i dont get it this going to fix it ??? Or waiting for upgrade(if we do when the upgrade come) im not so good in this Mechani things

sorry for bad english .