Long Url for custom controller taking too much time to load, Nopcommerce 4.5

1 个月 前
Below work instantly:
https://localhost:5001/carparts/sealing-cap-washer-fluid-tank
https://localhost:5001/carparts/relay-wipe-wash-interval
https://localhost:5001/carparts/control-unit-wipe-wash-interval
https://localhost:5001/carparts/washer-fluid-tank-window-cleaning
https://localhost:5001/carparts/sensor-wash-water-level
https://localhost:5001/carparts/gasket-washer-fluid-tank


Takes ages to/never reach controller:
https://localhost:5001/carparts/level-control-switch-windscreen-washer-tank    


Everything is the same between the two URLS so not making any sense why it is doing that if I change the url to :
https://localhost:5001/carparts/level-control-switch-windscreen
works instantly again.

Test based on length of SLUG so below work instantly:

boost-pressure-control-valve-2
holding-clamp-charger-air-hose-2
valve-compressor-bypass-flap-2
seal-water-connector-charger-2
seal-ring-oil-outlet-charger-2


However, the bigger the URL gets the slower the response gets, below take too long/never reach the middleware,

repair-kit-suspension-strut-support-mount-3
cable-repair-set-fuel-pressure-sensor-3



KEEPING NOTE:

Issue is only when /carparts/  is introduced in url:

https://localhost:5001/carparts/magnetic-clutch-air-conditioner-compressor


This is instant :
https://localhost:5001/magnetic-clutch-air-conditioner-compressor


Both above go to different controllers but just telling only the CategoryName is not the issue maybe the whole URL length is the issue?  I changed the SLUG for the above to: switch-windscreen-washer-tank and it worked fine.

Any category slug which is more than 32 characters after :https://localhost:5001/carparts/
Does not work.

What is going on here as really confused why long SLUG don't work like smaller ones. What am I missing here?
1 个月 前
RE: ... localhost ... "never reach"
Are you running in Visual Studio?
Check the Output window in VS for messages that may help.
Check System > Log for any errors.
Check browser dev tools Console and Network tab.
1 个月 前
I have tested locally and live, the long URLS gets resolved maybe after 10 min or similar but,
There is no error as it does get resolved after taking a lot of time.

Clearly this is a bug that needs to be sorted asap. I have tried with many URLS each one above 32-33 is bound to timeout after trying to load for minutes.

For example, this URL was never loading (waited for minutes):
https://localhost:5001/carparts/repair-kit-wheel-sensor-tyre-pressure-monitoring-system

Changed to :
https://localhost:5001/carparts/repair-kit-tpms-wheel-sensor


Works Instantly!