https://bz.apache.org/SpamAssassin/show_bug.cgi?id=8101

Sidney Markowitz <sid...@sidney.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|FIXED                       |---

--- Comment #7 from Sidney Markowitz <sid...@sidney.com> ---
(In reply to Christer Mjellem Strand from comment #6)

I'll reopen this at least long enough to take a look. Since we haven't had a
release that includes this issue, it is no big deal to reopen.

> https://ml-trk.com/
> aff_c?offer_id=8822&aff_id=37119&url_id=0_15409_15410_15411_15412_15413&aff_s
> ub5=email&source=s002
> 
> Returns a location header of:
> 
> /rd.html?go=https%3A%2F%2Fwww.SingleUkrainianBeauty.com%2Findex.
> php%2Fpromote%2Fclick%3Faid%3D2354%26oid%3DCP231375%26qpid_offer_id%3DSUB_235
> 084TSAEI%26qpid_subid%3D37119%26qpid_clickid%3D45_37119_8822_52c5875f9b6d77a8
> b48d37630ad127b4%26source_tag%3Ds002

If that is not recognized as a redirect to a local page and handled by looping
to process it, then that should be fixed within the scope of this issue.

However, it is a separate issue that it is not detected as a redirect to the
urldecoded form of the URL that comes after the ?go=

If I use curl to get the body of the /rd.html?go=... URL, I see it returns a
page with Javascript that does a redirect to the urldecoded specified URL. The
plugin will have no way of recognizing the /rd.html?go= form of the redirect
unless we add it as a special case when handling ml-trk URLs. I've opened bug
8114 for dealing with that, and will consider if it is worth doing.

However, it is strange that when I run

curl -I
'https://ml-trk.com/aff_c?offer_id=8822&aff_id=37119&url_id=0_15409_15410_15411_15412_15413&aff_sub5=email&source=s002'

it comes back with a 302 redirect with a location header of the
SingleUkrainianBeauty URL, not what you say the logs showed.

I'll try running it through SpamAssassin to see if the way the plugin fetches
the URL gets different results than curl -I, or whether the ml-trk site is
changing behavior.

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to