Am I missing aff clicks? TCP_MISS/301

[zelvmoney]

I have a domain in which I promote just one offer: mydomain.com

So I hide my aff link on a php file (redirect 301) on go.mydomain.com in order to get a nice aff link; so...

I saw my cpanel report for the subdomain (in which I only have the php file at the root) -> go.mydomain.com and I saw a lot:

Http Code: TCP_MISS/301 Date: :: Http Version: 202.54.86.51 Size in Bytes: 604
Referer: GET
Agent: hxxp://go.mysite.com/ - FIRST_UP_PARENT/127.0.0.1 text/html

I also saw (which is the ok occurence, right)

Http Code: 301 Date: Nov 28 02:25:15 Http Version: HTTP/1.1 Size in Bytes: 604
Referer: hxxp://mysite.com/
Agent: Mozilla/4.0

What does TCP_MISS/301 mean? Am I'm missing clicks? Thanks in advance

 

[jryan21]

MISS means the document being requested was not in the web server's cache and the actual document had to be retrieved. The 301 means the document being requested at that particular location is actually an (permanent) alias for its real location. Either way, it is still recorded as a document request and shouldn't affect your number of clicks.

Sometimes, when you get a lot of MISS responses for a particular document, you can (auto or manually) have the server cache it to save bandwidth.

 

[zelvmoney]

Either way, it is still recorded as a document request and shouldn't affect your number of clicks.

Thanks for your answer! But I didn´t understood. Does the visitor really went to the offer page? Does the redirect worked even when I have the 301 miss in the log?

Sometimes, when you get a lot of MISS responses for a particular document, you can (auto or manually) have the server cache it to save bandwidth.

I'm running on shared hosting; How can I do that?

Thanks in advance

 

[jryan21]

Yes, the visitor went to the correct location; those messages are describing some things that the server did internally.

Unless you are getting 100000s of requests a day or are in danger of using your allocated bandwidth, it's probably not worth your trouble to do caching.

 

[zelvmoney]

Yes, the visitor went to the correct location; those messages are describing some things that the server did internally.

Unless you are getting 100000s of requests a day or are in danger of using your allocated bandwidth, it's probably not worth your trouble to do caching.

ok, thanks for your answer