|
|
|||||||||
|
|||||||||
|
|||||||||
| |
|||
| |||||||||
![]() |
|
|
«
Previous Thread
|
Next Thread
»
|
Thread Tools | Search this Thread | Display Modes |
|
|
|
SlickEdit: Code in over 40 languages across 7 platforms. SlickEdit’s unmatched power, speed, and flexibility allows even the most accomplished developers to write better code faster. Download a free trial today! |
|
#1
|
|||
|
|||
|
ExpiresActive problem with .js and XP
I've been experiencing some problems with ExpiresActive and external js files. ExpiresActive is set to 1 second, which works great with windows 98 and 2000. However, not that well with XP - it returns js errors, causing the script not to load properly. I've tried to change it from 1 sec to 10 min, but that doesn't help. I believe it might have something to do with the XP Security Package (SP) 1. Has anyone else encountered similiar problems and if yes, did you find any solution to it?
|
|
#2
|
|||
|
|||
|
A friend of mine has that, and they have to contantly put thier security down quite often to get file transfers or downloads to work. What I've found with my XP is, there are certain types of files you may try to send, recieve in emails or thru a Priv Chat system or by online downloading or even switching within XP, that the security blocks or changes the transfer to protect your system. dll files among other types, or outside brand name files etc.
|
![]() |
| Viewing: Dev Articles Community Forums > Web Design > Web Server Configuration > ExpiresActive problem with .js and XP |
| Thread Tools | Search this Thread |
| Display Modes | Rate This Thread |
|
|
|
|