Skip to content
This repository has been archived by the owner on Apr 30, 2021. It is now read-only.

[AChecker] uploading file problem #74

Open
lamu84 opened this issue Mar 8, 2018 · 5 comments
Open

[AChecker] uploading file problem #74

lamu84 opened this issue Mar 8, 2018 · 5 comments

Comments

@lamu84
Copy link

lamu84 commented Mar 8, 2018

Hi,
I tried to run both local and on line, this file:(attached 087016 )
(I have this problems only with some files, and with others don't, all files in the same directory)
087016.zip

Local version AChecker 1.3
Xampp Php 5.3.0
Browser Mozilla
Local AChecker returns me error.(like cannoct connect to url)
On line version runs correctly.
The local AChecker error could be related to the file or something else?
Could you please try to run in local this file and tell me if it runs correctly?
Thanks.

@cindyli
Copy link
Contributor

cindyli commented Mar 8, 2018

Hi @lamu84, I tried the given html file with my local AChecker thru the tab "html file upload", the validation went thru and returned 48 known problems and 328 potential problems.

@lamu84
Copy link
Author

lamu84 commented Mar 12, 2018

did you do some improvement or tuning to your achecker build? because i still have this problem uploading the file.
I have the same error pasting code html instead of uploading.
Thanks again.

@cindyli
Copy link
Contributor

cindyli commented Mar 12, 2018

No, I didn't. The investigation might happen at the next development cycle.

@lamu84
Copy link
Author

lamu84 commented Mar 12, 2018

May i ask you what kind of hardware (CPU, RAM) and softfware (OS, web platform for example xampp ) do you use to do your test? thanks.
is it possible that could be an HW limit ?

@cindyli
Copy link
Contributor

cindyli commented Mar 12, 2018

@lamu84, my local AChecker runs on MacOS 10.13.3, MAMP environment with PHP 5.6.3 and MySQL 5.6.38, firefox 58.0.2 and chrome 64.

If your local achecker reports "cannot connect to url", open url in a separate browser to make sure it's accessible. If the problem persists, check PHP error log to see if there's any errors or warnings. If nothing looks wrong, debug at this line where the url is fetched to find out what's wrong with file_get_contents().

The validation does relate to the CPU processing power. It's a known issue that when the validated content contains deep nested html tags, the validation may not be able to finish before the timeout limit reaches. In this case, AChecker usually returns 500 or 502 "internal server error". You should be able to find a couple of existing bug reports related to this issue.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants