Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FS#2451 - [ath79] HTTP response 408 if using SW flow offload #6144

Closed
openwrt-bot opened this issue Aug 19, 2019 · 3 comments
Closed

FS#2451 - [ath79] HTTP response 408 if using SW flow offload #6144

openwrt-bot opened this issue Aug 19, 2019 · 3 comments
Labels

Comments

@openwrt-bot
Copy link

vinibali:

Hell there,

I'm using one of the latest snapshot builds (r10280-2b074654b0) on my 1043 V2.
In overall I feel the software flow offload makes the browsing a bit more laggy and strange.
Sometimes Google fails to refresh the map, while I'm zooming in or out, just like Duckduckgo fails to display image results.
But I have one reproducible problematic site load at: [[https://www.jofogas.hu/]].
This is a Hungarian online marketplace, which ends up showing 408 HTTP code after 5 seconds. I've got the same response, but even after I switch the flow offload off, it's back in normal.

Is that a know bug with the flow offload?
Is there any way I can help to figure out what's wrong in this case?

Regards

@openwrt-bot
Copy link
Author

vinibali:

I've got a similar experience, while submitting this exact bugreport.
The browser was unable to refresh the page after I clicked on the submit button.
I tried to upload the report twice with flow offload. Finally I was able to right after I switched this function off.

@openwrt-bot
Copy link
Author

psyborg:

does it still happen when you apply patch from #2266 ?

@openwrt-bot
Copy link
Author

vinibali:

will this merged soon?
i dont really want to build, if i can get the same package from the snapshot repo :)

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

No branches or pull requests

1 participant