[wp-hackers] Dowloading 18.104.22.168
laebshade at gmail.com
Thu Jun 30 19:27:04 GMT 2005
Why not just put a hard link to the actual file?
On 6/29/05, Michael D Adams <mikea at turbonet.com> wrote:
> If there is a problem, it could easily be with the method rather than
> with this particular instance. Supposing that is the case, "fixing
> 22.214.171.124" would fix all future redirects as well. But I agree, there
> are likely more important things going on at the moment.
> On Jun 29, 2005, at 11:19 AM, Robert Deaton wrote:
> > Shouldn't bother fixing 126.96.36.199, we need 188.8.131.52 soon anyways
> > On 6/29/05, Podz <podz at tamba2.org.uk> wrote:
> >> Michael D Adams wrote:
> >>> http://wordpress.org/support/topic/37805
> >>> Could the voodoo behind the latest.zip -> wordpress-184.108.40.206.zip
> >>> redirection be stopping a few people, or is this a bad something-or-
> >>> other on the poster's end?
> >> This has happened before - empty files, 1K downloads, no downloads
> >> and
> >> on each browser. Genuine Gremlins I think :)
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
- Mark Shields
More information about the wp-hackers