Peaceful greetings Google Group Members and Mr. Di Pierro.
First of all, thanks to all of you, web2py dev team, group members,for
giving us the power of deploying with such a complete python web framework.
I can imagine the heavy load of work behind from its beginning, to present
day.
The thin
Peaceful Greetings Web2Py Group!
In my first glances of practicing and implementing this awesome framework,
came across with some doubts with the *authorization* topic.
In general database, server and services good practices, hand to hand with
security, What do you think that is the best? (base
Greetings Web2Py fellows!
While working with the DAL and some views I faced wall when I looked at the
POST constructor from API. So the first question is simple.
Is there any way to only catch a value from the POST constructor and do
whatever I want inside the controller 'default.py' in order t
Dude!!! Thanks a lot!!! It worked like expected...
Just for the record, in case someone face this problem.
I set it up like suggested:
def POST(*args, **vars):
if (some_controller_method(vars['entry_value'])):
print "The Output"
print str(vars['entry_value'])
else:
Currently working only with the 'auth_user' table, and I must say that I
works like expected. Following the advices from Mr. Di Pierro, won't make
any split of types of users or something like that, and will keep working
and improving the use of this table and database in general. Thanks a
lot
Astonishing support and goodwill, thanks a lot again Mr. Di Pierro!
I will implement it that way in order to keep improving the infrastructure
and performance of the back-end.
Have a wonderful night and week! :D
--
Resources:
- http://web2py.com
- http://web2py.com/book (Documentation)
- http
Greetings people! :D
Is there some way to do password recovery, let's say, from curl for example?
The main target is to get a SAFE WAY to restore password through API in
order to use it, let's say, in some mobile application or somewhere that is
not the web page... Is that possible?
Have a ni
Greetins community! Thanks for passing by, hope we can get nice data from
this issue.
So, we're creating a backend application that receives POST petitions with
basic http auth from an Android app, no cookies r advanced topics for
sessions, I want to get there, but I'm kinda new to this... Thi
Greetings again!!! THANKS FOR YOUR EARLY ANSWER! I'm very sorry for being
late... Kinda busy and daily life stuff goin' on.
Well, the issue happens with these functions.
The android device sends a POST request in order to get some data, every 30
secs. To this functions... Obviously.
http://loc
Thanks for the support and figuring it out with the community!
Providing answers in the right order:
@Anthony, the HTTPS protocol is not yet implemented, first we need the
transactions fully working, so HTTP protocol is used meanwhile. We're not
using web browsers, is the Android App that gener
Hi José! Thanks for suporting too! C:
I'm learning about this framework, and I have a glimpse of what the browser
does in data exchange between web pages and backend stuff... But, in this
application, I'm afraid we want to provide the right interface for the
backend.
So, no web forms, at least
Thanks José! :D
I'm afraid it already does help me... :3
In the implementation of that slice, Leonel Cámara & Massimo came to
suggest another way of having POST requests for the backend... So, a
modification of it he suggested in:
https://groups.google.com/d/msg/web2py/wfHtQ6P2Gmo/lrljWW1LBEIJ
That was fast, thanks! :D
>
> *
>
> *... By default, Auth protects logins against cross-site request forgeries
> (CSRF). This is actually provided by web2py's standard CSRF protection
> whenever forms are generated in a session. However, under some
> circumstance
Wow, thanks! I can feel the love here at the forums!
@José, I'll make the Bruno's approach at local PC in order to apply those
good practices exposed without risk, failure isolation has my attention and
I'm definitely in favor of isolation, so, will do, and catch up more with
clients as stated.
I'll make good use of your recommendations, will evaluate the session
persistence variables, in order to distinguish the parameters between
functions, and/or (will think and test) get rid of session or leave them
for good, because of the upcoming views that will display in admin
interface or so
UX, the registration is done via Android and HTTP
request. We implement e-mail verification, and want to display a custom
view web page that tells the user the succesfull transaction.
Thanks a lot!!! Buena vibra!
Yours, sincerely Jon M.
--
Resources:
- http://web2py.com
- http://web2py.com
Woah!!! :D
Thanks, thanks, thanks!
So, at db.py I ended using one of these:
#auth.settings.verify_email_next =
('http:default/account_confirmation')
auth.settings.verify_email_next = URL ('default', args=
'account_confirmation')
Both work, fully working... When tapping the URL at G
17 matches
Mail list logo
