I think you should be worried about users that refuse to reply with
the cookie thus
the session is pretty much useless in this case (crawlers usually
don't hold the cookie).
In this case you need to track the users by IP address.
I would solve this problem on the Apache server side with
I would like to know if there's a way to know if a record inserted is
new in the postSave function within a model?
--
If you want to report a vulnerability issue on symfony, please send it to
security at symfony-project.com
You received this message because you are subscribed to the Google
Thanks again for the response. Even if my question wasn't about
storing sessions, it's a nice article!
Saving session by ip ... what if $_SERVER['REMOTE_ADDR'] is not set ?
or if it's giving you only a proxies ip? you would need something like
that and even won't be sure to get an ip:
function
Saving session by ip ... what if $_SERVER['REMOTE_ADDR'] is not set ?
That value should always be set.
If there is a proxy between the client and the server it will be the
proxy server IP address and maybe set up
in the HTTP header as X-Forwarded-For.
Anyway... as I mentioned my main
I don't think that you can do this given that these are decided on the
application level (not module level).
What you can do is do a forward to your own 404 page depending on the
request once you are in the 404
action.
gabriel
On Jun 4, 8:09 pm, Carlos Jorge Andrade carlos.andr...@gmail.com
why not use postInsert() ?
Tugdual
2010/6/5 PachinSV pachi...@gmail.com
I would like to know if there's a way to know if a record inserted is
new in the postSave function within a model?
--
If you want to report a vulnerability issue on symfony, please send it to
security at
Thank you guys, this is awesome!
--
Денис Горбачев,
Начальник отдела Web-разработок ЗАО ТруОфис
http://www.trueoffice.ru/
+7 929 619-35-88
--
If you want to report a vulnerability issue on symfony, please send it to
security at symfony-project.com
You received this message because you are
French;
OK, en Français:
- Nous avons besoin de développeurs symfony.
;-)
Tugdual
--
If you want to report a vulnerability issue on symfony, please send it to
security at symfony-project.com
You received this message because you are subscribed to the Google
Groups symfony users group.
To
Hello Denis
This is in Malayalam (India - Kerala)
ഞങ്ങള്ക്ക് സിംഫണി പ്രോഗ്രമ്മേഴ്സിനെ ആവശ്യമുണ്ട്
Thanks and Regards
Arun Raj R
http://techaspirant.com
--
If you want to report a vulnerability issue on symfony, please send it to
security at symfony-project.com
You received this message
Sorry i forgot to add first line
This is in Malayalam (India - Kerala)
ശരി , പച്ച മലയാളത്തില് :
--ഞങ്ങള്ക്ക് സിംഫണി പ്രോഗ്രമ്മേഴ്സിനെ ആവശ്യമുണ്ട്.
2010/6/5 Arun Raj R aru...@gmail.com
Hello Denis
This is in Malayalam (India - Kerala)
ഞങ്ങള്ക്ക് സിംഫണി പ്രോഗ്രമ്മേഴ്സിനെ ആവശ്യമുണ്ട്
My suggestion in this case is to use the difference between GET/POST.
That sounds great to me!
I would keep in session (or the URL) the filter used and not the
actual results.
how do you secure, that one cannot bypass the post-form, by url-
manipulation?
--
If you want to report a
how do you secure, that one cannot bypass the post-form, by url-
manipulation?
You can not really do that, they can do whatever they want in the
request.
One thing that you have to do is to enforce a session upon the users
that get to search form - by requesting login for instance.
To
On 31 May 2010, at 10:27, Richard D Shank wrote:
I'm getting ready to start building a store for a music site. It will only
be virtual products for now (mp3 downloads), but it will have some of the
elements you are needing.
Save yourself a whole heap of trouble and use Magento.
I used
I'm going to try that my friend.
On 5 jun, 03:16, Tugdual SAUNIER tucks...@gmail.com wrote:
why not use postInsert() ?
Tugdual
2010/6/5 PachinSV pachi...@gmail.com
I would like to know if there's a way to know if a record inserted is
new in the postSave function within a model?
--
I tried this out; the sfGuardUserProfile part of my
config/doctrine/schema.yml looks like this:
sfGuardUserProfile:
tableName: sf_guard_user_profile
columns:
user_id:
type: bigint(20)
notnull: true
default:
unsigned: false
primary: false
unique: false
I noticed if I view the source of the webpage i do not see the
FB.Init() method. Here is my layout.php
?php use_helper('sfFacebookConnect')?
!DOCTYPE html PUBLIC -//W3C//DTD XHTML 1.0 Strict//EN http://
www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd
html xmlns=http://www.w3.org/1999/xhtml;
Ok, so the best practice is Keep It Stupid Simple (KISS) with some
simple session-checks (and yes, the users need to be logged in for
searching)
Thanks for the great responses pghoratiu/gabriel!
On 5 Jun., 13:37, pghoratiu pghora...@gmail.com wrote:
how do you secure, that one cannot bypass
Hey there,
this is the standard behavior. Most plugins define the package
directory similar to this:
_attributes: { package: plugins.sfGuardPlugin.lib.model }
This makes the model live in the plugin directory.
Daniel
On Jun 3, 8:06 am, AgusQuiroga agusquir...@gmail.com wrote:
Hi,
I
Taking a look at
plugins/sfDoctrineGuardPlugin/config/doctrine/schema.yml, all of the id
columns use integer(4). Isn't this what the user_id type should be?
=
It should be type: integer(4)
columns:
user_id:
type: integer(4)
notnull: true
gabriel
--
If you want
On Fri, 4 Jun 2010, Ragnis wrote:
Why does it even have to be so complicated..
Actually its not, symfony is quite flexible but it *does* require you read
and learn the framework to use it well.
--
--
If you want to report a vulnerability issue on symfony, please send it to
security at
20 matches
Mail list logo
