Re^3: IPC::Open, Parallel::ForkManager, or Sockets::IO for parallelizing?

have some questions about how it should handle many (most?) HTTPS sites.

Yeah, it seems to be pretty much all of them, which is a real shame. I guess it must have been about 6 or 7 years ago that I last used LWP::Parallel for anything serious and back then this wasn't really an issue. In the meantime the heavy hand of Google has de-facto forced most of the web over onto HTTPS and now this is a major consideration.

Having tested this briefly against one of my own sites it does actually appear to be downloading the content in that the server receives, accepts and serves the request OK. It's just that the user agent has some sort of internal problem with the response.

It might be worth raising a ticket although there are plenty open. Still, it would alert other users to the problem.

🦛

Comment on Re^3: IPC::Open, Parallel::ForkManager, or Sockets::IO for parallelizing?

Replies are listed 'Best First'.
Re^4: IPC::Open, Parallel::ForkManager, or Sockets::IO for parallelizing? by mldvx4 (Friar) on Oct 03, 2023 at 12:50 UTC
I'm willing to try making a bug report. Is there an alternate approach to raising a ticket, other than that link? The self-censored comment: I ask because the link offered goes not to a web page or web site but a "web app", and a broken "web app" at that. After 10 minutes of faffing about with broken "web app", I was able to create an account and log in. However, after an additional 15 minutes I was not able to make any headway in actually getting a complete web form in order to report a bug let alone actually report a bug. I enjoy Perl a lot and am really grateful for all the knowledge here here but have zero tolerance for javascript, especially when it is abused to block what used to be a simple activity. :(	[reply]
Re^5: IPC::Open, Parallel::ForkManager, or Sockets::IO for parallelizing? by kcott (Archbishop) on Oct 03, 2023 at 14:02 UTC
"Is there an alternate approach to raising a ticket ..." Take a look at "How to use rt.cpan.org". It provides a variety of information including bug reporting; the email option may be more to your liking. There's links to other information which may help you with problems that you're experiencing. I've raised quite a few bug reports over the years but always used email; I can't provide any direct help with the "web app" you describe. — Ken	[reply]
Re^5: IPC::Open, Parallel::ForkManager, or Sockets::IO for parallelizing? by hippo (Archbishop) on Oct 03, 2023 at 14:07 UTC
RT certainly used to be fine with JS disabled. Perhaps there has been some change in that regard. Anyway, from the RT homepage: To submit a bug report for a given distribution by email, send mail to bug-<distribution-name>@rt.cpan.org, where "<distribution-name>" is something like DBIx-SearchBuilder or Class-DBI or Acme-Current-Forever. Use search to find name of a distribution. In this case the distribution name is `ParallelUserAgent` PS. The direct link to create a ticket for any dist is here. 🦛	[reply]
Re^6: IPC::Open, Parallel::ForkManager, or Sockets::IO for parallelizing? by mldvx4 (Friar) on Oct 03, 2023 at 15:22 UTC
To be clear, RT.cpan.org does not work with javascript fully enabled either. At scale, if there is a low threshold for reporting bugs then there will be bug reports and if there is a high threshold then there won't be bug reports. I'd like for there to be a relatively smooth and problem free path for bug reporting so that the project can survive. In this case the distribution name is `ParallelUserAgent` Thanks, though it may take some time to figure out the way through.	[reply] [d/l]